Skip to main content

​
Overview

Salesforce CRM leads, contacts, accounts, opportunities, cases, tasks, events, associations, and SOQL search. Category: Crm
Catalog status: active

​
Supported capabilities and connector actions

​
Direction

  • P2HS → Salesforce: Yes — supported actions can send data or requests to the provider.
  • Salesforce → P2HS: Yes — the catalog declares inbound triggers.
  • Webhooks: Event delivery is represented by the declared triggers.

​
Prerequisites

  • A Salesforce account with permission to create or authorize the connection.
  • The credentials or authorization flow required by P2HS (Oauth).
  • Any provider-side account, workspace, repository, store, or sending-domain permissions required for the selected capability.

​
Connect the integration

  1. Open the P2HS dashboard.
  2. Select the project or workspace where the connector will be used.
  3. Open Integrations and choose Salesforce.
  4. Select Connect and complete the provider authorization or credential form.
  5. Save the connection and run the verification check.
  6. Bind the connection to a compatible capability, App Block, or Feature Pack.

​
Credentials and configuration

Authentication: Oauth. The current catalog requires these credential fields:
  • access_token
  • refresh_token
  • instance_url
Configurable fields exposed by the connector:
  • api_version
P2HS stores connector credentials as managed secrets. Rotate or revoke them from the connection settings; do not commit them to source code or expose them in browser code.

​
Generated applications

After Salesforce is connected, compatible capabilities and composed application features can bind to the connection. The generated application should call the approved P2HS capability rather than embedding Salesforce credentials.

​
Events and webhooks

The catalog declares these inbound events:
  • lead_created — Lead created
  • lead_updated — Lead updated
  • lead_deleted — Lead deleted
  • contact_created — Contact created
  • contact_updated — Contact updated
  • contact_deleted — Contact deleted
  • account_created — Account created
  • account_updated — Account updated
  • account_deleted — Account deleted
  • opportunity_created — Opportunity created
  • opportunity_updated — Opportunity updated
  • opportunity_deleted — Opportunity deleted
  • case_created — Case created
  • case_updated — Case updated
Inbound events are verified and processed by the P2HS integration contract before application state is updated.

​
Troubleshooting

  • Authentication failed: confirm the credential or authorization flow and the provider account selected.
  • Permission denied: verify that the provider account can access the configured resource and action.
  • Action unavailable: confirm that the capability is admitted for the project and supported by this connector.
  • Event not received: check the connection status, provider event configuration, and the project environment.

​
Disconnect or rotate credentials

Update or revoke the connection from the project or workspace Integrations settings. Dependent capabilities may stop working after disconnecting; reconnect and verify the binding before retrying the application flow.