Describe CRM object
Read an object definition and field metadata, without querying customer records.
Connector library
Salesforce CRM Records connector.
Describe CRM objects, retrieve Account/Contact/Lead records and create one explicitly confirmed CRM record through Salesforce REST API.
Connector download
Download Salesforce CRM Records
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
- 0.1.0.0
- Release
- 2026-10-05
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- API Base URL, API Version, Request Budget (ms)
- Package size
- 7 KB
- SHA-256
007dc05ee314252adefb7e9d7299f52bf834ac280274a981287dc78d4745c924- Notes
- Read release notes
Included in this version
Included actions
Implemented in v0.1.0.0. Use a separate flow trigger; no webhook trigger is included.
Get CRM record
Read one Account, Contact or Lead by its Salesforce record ID.
Create CRM record
Create one object record from a bounded field map after explicit confirmation.
Vendor API
API and access
Implementation considerations
- Supported scope: Describe CRM objects, retrieve Account/Contact/Lead records and create one explicitly confirmed CRM record through Salesforce REST API.
- Select a bearer-token credential containing an OAuth access token issued for the Salesforce org. Set the trusted HTTPS instance origin ending in .salesforce.com and the API version enabled for that org, such as v65.0. No token grant or client secret exchange is implemented.
- Account, Contact and Lead only. No arbitrary SOQL, Marketing Cloud, bulk jobs, token refresh or update/delete. Creation requires confirmation and can create duplicates if replayed. Reconcile an uncertain creation against CRM records before resubmitting. Object field permissions and required fields remain org-specific. Each HTTP action uses a 1–8 second request budget, a 128 KiB request-body limit and a 1 MiB raw JSON response limit. Redirects, automatic paging and automatic retries are disabled. Responses exceeding these bounds fail rather than being truncated. Configure only trusted HTTPS service origins and map connection settings from flow properties.
- New independent connector registration. Existing legacy flows require deliberate action and credential remapping. Hosted import and live service validation remain pending.
Related connectors
More in Enterprise, ERP & HR APIs
Support
Need help with Salesforce CRM Records?
Tell us what you need to connect or change.