Integration reference

Salesforce Trigger and Action reference

Start Workflows from new, updated, or deleted Salesforce records and manage standard or custom objects through REST, SOQL, SOSL, and composite APIs.

Authentication

Install the FastHook Packaged External Client App in the Salesforce organization, then connect an authorized Salesforce user through OAuth. FastHook stores the access and refresh tokens encrypted.

• Trigger account type: oauth2; reconnect by oauth.
• Action connection type: oauth2; available modes: Connected Salesforce account.

Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.

Scopes and permissions

Base Trigger authorization requests: api, refresh_token.

Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.

Use Salesforce as a Trigger

The current provider manifest contains 9 available Trigger definitions. Representative definitions include:

• New Record
• Updated Record
• Deleted Record
• New Lead
• New Opportunity

Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.

Use Salesforce Actions

The current Action manifest contains 12 operations. Representative Actions include:

• Create Record
• Update Record
• Upsert Record
• Run SOQL Query
• Create Multiple Records

The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.

Build a Workflow

1. Create a Source using a Salesforce Trigger definition.
2. Create a Workflow with that Source as its Trigger.
3. Add the required Salesforce Action and select the connected account.
4. Map Trigger or earlier-Step data into the Action fields with the field picker.
5. Add a Filter, Paths, Delay, or Transformation when the route needs it.
6. Activate the Workflow, produce a controlled event, and verify the run in Audit and in Salesforce.

Troubleshooting Salesforce

The account is missing or cannot be selected

Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.

A resource picker is empty

Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.

The editor asks for additional scopes

Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.

An active Workflow returns 401, 403, or a permission error

Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.

The provider returns 429 or a temporary 5xx

Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.

Provider-specific checks

• FastHook loads the connected organization's objects and fields through Salesforce Describe metadata, including custom objects and custom fields.
• Polling Sources establish a baseline on the first check and then request changes every five minutes. Deleted-record history is limited by Salesforce's deleted-record retention window.
• The connected user must have API access plus object-level and field-level permissions for every record the Workflow reads or writes.
• Create Multiple Records uses Salesforce Composite SObject Collections and accepts up to 200 records per request.
• Custom API Request stays on the OAuth instance URL and the negotiated REST API version; it cannot override the host or Authorization header.
• Record output schemas stay open because each Salesforce organization can define different custom objects and fields. Describe Object returns the authoritative runtime schema.

Next

• Explore Salesforce integrations
• Trigger configuration
• Action configuration
• Data mapping
• Error handling
• Authentication and permissions
• All automation integrations