The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 6, 2026 5:45pm

PR Summary

Medium Risk
Adds new webhook trigger configurations and wires them into the Salesforce block/trigger registry; risk is mainly around correct trigger selection/output shape and webhook payload handling for new endpoints.

Overview
Adds six new Salesforce webhook-based triggers (record created/updated/deleted, opportunity stage changed, case status changed, and a generic “all events” webhook) with standardized sub-block UI, setup instructions, and declared outputs.

Registers these triggers in TRIGGER_REGISTRY and updates the SalesforceBlock to enable triggers, advertise the available trigger IDs, and merge the trigger-specific subBlocks via getTrigger(...) so they appear in the block configuration UI.

^{Reviewed by Cursor Bugbot for commit d67ab32. Configure here.}

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

Greptile Summary

This PR adds 6 Salesforce webhook triggers (record created/updated/deleted, opportunity stage changed, case status changed, and a generic catch-all) following the established pattern used by Lemlist, Cal.com, and Confluence integrations. The code is well-structured with shared utilities in utils.ts, correctly registered in the trigger registry, and properly wired into the Salesforce block config.

Two P2 UX issues were found in utils.ts:

• The setup instruction step 3 for "Opportunity Stage Changed" and "Case Status Changed" references trigger condition names that don't exist in Salesforce Flow UI, which will confuse users during manual setup.
• The changedFields output is included in buildSalesforceRecordOutputs() which is shared across created, updated, and deleted triggers — but changedFields is only meaningful for update events, and seeing it as an available output on created/deleted triggers will mislead workflow authors.

Confidence Score: 5/5

Safe to merge — functionally correct code that follows established patterns; only P2 UX/documentation issues remain

Both findings are P2 issues in setup instruction text and output schema semantics that do not affect runtime behavior or data integrity. All 6 triggers are correctly registered, the block wiring is correct, and the code structure mirrors proven existing integrations.

apps/sim/triggers/salesforce/utils.ts — incorrect Flow trigger condition names for Opportunity Stage Changed and Case Status Changed, and changedFields on created/deleted outputs

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant SF as Salesforce Flow
    participant WH as Sim Webhook Endpoint
    participant TR as Trigger Registry
    participant WF as Workflow Engine

    SF->>WH: POST /webhook/{path}<br/>(JSON: eventType, objectType, record, ...)
    WH->>TR: Lookup TriggerConfig by triggerId
    Note over TR: salesforce_record_created<br/>salesforce_record_updated<br/>salesforce_record_deleted<br/>salesforce_opportunity_stage_changed<br/>salesforce_case_status_changed<br/>salesforce_webhook
    TR-->>WH: TriggerConfig (outputs schema)
    WH->>WF: Execute workflow with mapped outputs
    WF-->>SF: 200 OK

_{Reviews (2): Last reviewed commit: "fix(triggers): address PR review — remov..." | Re-trigger Greptile}

@greptile

@cursor review