feat(integrations): add Gong incident.io Railway and New Relic#4663
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryMedium Risk Overview Extends Gong with a new Extends incident.io by adding workflow creation, escalation-path listing, and new filters/inputs (sorting/filter mode, incident mode, user filters, schedule override Reviewed by Cursor Bugbot for commit b5fbb25. Configure here. |
Greptile SummaryThis PR adds four new integrations — Gong, incident.io, New Relic, and Railway — with full tool, block, registry, icon, landing, and docs wiring. Existing incident.io tools receive significant improvements: stricter JSON parsing for workflow operations, API schema alignment (schedule entries, escalations, escalation paths), and removal of the silent-fallback logger-based parsing that previously swallowed JSON errors.
Confidence Score: 5/5Safe to merge. All four integrations are additive with no changes to shared infrastructure or existing auth flows. All previously flagged issues (workflow JSON silent fallback, entityGuid injection, compactVariables empty-string filtering) have been resolved on the branch. The new tools follow established patterns, credentials use the correct visibility, and GraphQL inputs are either parameterised or thoroughly validated. The remaining findings are minor quality improvements that do not affect correctness at runtime. No files require special attention. The incident.io tools consistently omit an HTTP error guard in transformResponse, but this is a pre-existing pattern shared across the integration and is not a regression introduced by this PR. Important Files Changed
Reviews (4): Last reviewed commit: "fix(gong): align list calls block valida..." | Re-trigger Greptile |
|
@greptile |
|
@cursor review |
|
@greptile |
|
@cursor review |
|
@greptile |
|
@cursor review |
|
@cursor review |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit b5fbb25. Configure here.
| if (params.user_slack_id) user.slack_user_id = params.user_slack_id | ||
|
|
||
| return { | ||
| layer_id: params.layer_id.trim(), |
There was a problem hiding this comment.
Empty override user sent
Medium Severity
The schedule override request always includes a user object even when no user_id, user_email, or user_slack_id is provided, so the body can be sent with {}. The block UI says one identifier is required, but the tool does not validate that before calling incident.io.
Reviewed by Cursor Bugbot for commit b5fbb25. Configure here.


Summary
Type of Change
Testing
Checklist