Connect a sales CRM.
Choose HubSpot, Pipedrive, or Salesforce in Sales Development. Zendesk is available for support escalations. Steadframe checks access, encrypts the credential, and sends newly approved leads directly to that CRM.
A mailbox is needed for reading prospect replies, drafting email, or sending follow-up. After connecting a CRM, use Send approved leads on its connection card to deliver leads approved before you connected it.
HubSpot
Send approved leads to HubSpot contacts or companies.
A HubSpot administrator must create a private app and share its access token with the Steadframe workspace administrator.
- 1
In HubSpot, open Settings → Integrations → Private Apps and create an app for Steadframe.
- 2
Grant crm.objects.contacts.read, crm.objects.contacts.write, crm.objects.companies.read, and crm.objects.companies.write.
- 3
Create the app, copy its access token, then open Steadframe → Sales Development → CRM connections → Add CRM.
- 4
Choose HubSpot, paste the token, and select Test and connect. The test reads a contact; the first lead delivery also checks write access.
What Steadframe sends: For an approved lead with an email address, Steadframe matches or creates a contact. Without an email address, it matches or creates a company by website domain.
Pipedrive
Send approved leads to Pipedrive people or organizations.
A Pipedrive user with API access and permission to manage people and organizations must provide their personal API token.
- 1
In Pipedrive, open Settings → Personal preferences → API and copy the token.
- 2
Open Steadframe → Sales Development → CRM connections → Add CRM, choose Pipedrive, and paste the token.
- 3
Select Test and connect. The test verifies account access; send an approved lead to confirm write permission.
What Steadframe sends: For an approved lead with an email address, Steadframe matches or creates a person. Without one, it creates an organization. Later deliveries update the linked record.
Salesforce
Send approved leads to Salesforce Leads.
A Salesforce administrator must create an external client app using OAuth client credentials and assign a run-as integration user with API and Lead read/write access.
- 1
In Salesforce Setup, create an External Client App and enable OAuth client credentials for it.
- 2
Assign its run-as integration user, grant that user API access and Lead read/write access, then copy the client ID and client secret.
- 3
Open Steadframe → Sales Development → CRM connections → Add CRM. Choose Salesforce and enter your My Domain URL, client ID, and client secret.
- 4
Select Test and connect. Steadframe obtains an OAuth access token; send an approved lead to confirm Lead write permission.
What Steadframe sends: Steadframe matches a Salesforce Lead by email when available, then updates it or creates a new Lead.
Zendesk helpdesk
Send support escalations to Zendesk tickets.
A Zendesk agent needs an API token with ticket access. This connection is for support conversations, not sales leads.
- 1
In Zendesk Admin Center, open Apps and integrations → APIs → Zendesk API and enable token access.
- 2
Create an API token. In Steadframe, choose Zendesk helpdesk and enter your subdomain, agent email, and token.
- 3
Select Test and connect. Support escalations can then create or update Zendesk tickets.
What Steadframe sends: Escalated support conversation details and transcript needed to create or update a ticket.
Can clients connect with one OAuth button?
Yes, after Steadframe registers its own application with each CRM provider.
That setup needs a provider-issued client ID, client secret or PKCE configuration, approved redirect URL, scopes, and token renewal. It is separate from a client's private app or API token. The direct connection form currently uses HubSpot and Pipedrive tokens; Salesforce uses OAuth client credentials supplied by the client's administrator. No one-click authorization button is available yet.
Troubleshooting
The connection check verifies access. A lead delivery verifies the write path.
- Connection test returns 401 or 403
- Check that the credential belongs to the intended CRM account, has not expired, and has the permissions listed above.
- Connection passes but a lead fails
- Grant write permission for the target record type, then use Send approved leads on the connection card to retry failed deliveries.
- I connected after leads were approved
- Use Send approved leads on the connection card. It sends up to five pending approved leads per request; repeat until the pending count reaches zero.
- I need to replace a credential
- Remove the old connection and add it again with a new credential. Leads remain in Steadframe.