feat(crowdstrike): add tools + validate whatsapp, shopify, trello#4123
feat(crowdstrike): add tools + validate whatsapp, shopify, trello#4123icecrasher321 merged 5 commits intostagingfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryMedium Risk Overview Hardens and aligns existing integrations. Trello auth/storage/routes and block params are tightened (canonical scopes, callback handling, stricter request parsing/validation, richer inputs like Reviewed by Cursor Bugbot for commit 7aa14ad. Configure here. |
Greptile SummaryThis PR adds three CrowdStrike Identity Protection tools (query sensors, get sensor details, get sensor aggregates) along with the corresponding block and docs, and fixes/validates the WhatsApp, Shopify, and Trello integrations. The CrowdStrike route correctly implements the two-step query-then-entities fetch pattern, the WhatsApp webhook provider gains HMAC signature verification and a richer Confidence Score: 5/5Safe to merge — all previously flagged P1 concerns are addressed and the only remaining finding is a P2 style cleanup. CrowdStrike tools are correctly scoped to identity-protection endpoints and all operations are covered by tests. The WhatsApp, Shopify, and Trello fixes are solid. The single remaining comment is about a redundant No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant UI as Sim Block UI
participant Route as /api/tools/crowdstrike/query
participant CS as CrowdStrike API
UI->>Route: POST {operation, clientId, clientSecret, cloud, filter?, limit?, offset?}
Route->>CS: POST /oauth2/token (client_credentials)
CS-->>Route: access_token
alt crowdstrike_query_sensors
Route->>CS: GET /identity-protection/queries/devices/v1
CS-->>Route: {resources: [id1, id2, ...]}
Route->>CS: POST /identity-protection/entities/devices/GET/v1 {ids}
CS-->>Route: {resources: [{device objects}]}
Route-->>UI: {sensors, count, pagination}
else crowdstrike_get_sensor_details
Route->>CS: POST /identity-protection/entities/devices/GET/v1 {ids}
CS-->>Route: {resources: [{device objects}]}
Route-->>UI: {sensors, count}
else crowdstrike_get_sensor_aggregates
Route->>CS: POST /identity-protection/aggregates/devices/GET/v1 {aggregateQuery}
CS-->>Route: {resources: [{buckets,...}]}
Route-->>UI: {aggregates, count}
end
Reviews (3): Last reviewed commit: "fix build" | Re-trigger Greptile |
|
@greptile |
|
bugbot run |
|
@greptile |
|
bugbot run |
|
bugbot run |
|
@greptile |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7aa14ad. Configure here.
| mutation fulfillmentCreateV2($fulfillment: FulfillmentV2Input!) { | ||
| fulfillmentCreateV2(fulfillment: $fulfillment) { | ||
| mutation fulfillmentCreate($fulfillment: FulfillmentInput!) { | ||
| fulfillmentCreate(fulfillment: $fulfillment) { |
There was a problem hiding this comment.
Fulfillment mutation name mismatches Shopify API version
Medium Severity
The GraphQL mutation was renamed from fulfillmentCreateV2 with FulfillmentV2Input to fulfillmentCreate with FulfillmentInput, and the response parsing changed from data.data?.fulfillmentCreateV2 to data.data?.fulfillmentCreate. However, the API URL still targets version 2024-10. The fulfillmentCreateV2 → fulfillmentCreate rename was introduced in a later API version. If the 2024-10 API doesn't recognize fulfillmentCreate/FulfillmentInput, fulfillment creation will fail with a GraphQL error.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 7aa14ad. Configure here.


Summary
Add crowdstrike tools.
Validate old blocks -- whatsapp, shopify, trello so they're in line and work.
Type of Change
Testing
Verified using docs.
Checklist