Integrations

What connects today, and how:a native connector, a webhook, or an API call are different things, and this section says which is which.

app.salescrew.io/settings

Settings: MCP tokens, integrations and the audit log

SalesCrew has fewer native, click-to-connect integrations than a large platform like HubSpot or GoHighLevel. Most connections run through webhooks, the API or the MCP server rather than an app-store listing. That trade produces fewer pre-built buttons and a more open connection point for anything that speaks MCP or reads a webhook.

What connects today

Integration	Mechanism	Status
Gmail, Outlook, cPanel mail	IMAP/SMTP mailbox connect	Live
Calendly	Webhook:bookings become meetings and inbound leads	Live
Apollo	Data-source provider for import and enrichment	Live
Instantly	Sender and domain registry sync	Live:send provider on the roadmap
Salesforce	Outbound send path for campaign pushes	Live
Vapi	Outbound calls	Live:inbound receptionist on the roadmap
Upwork, Fiverr	Full marketplace channel module	Live
GA4, Search Console, Bing, Google Ads, Meta Ads, PostHog	Read-only collectors into the marketing module	Live
Zapier, Make, n8n	Via outbound webhooks, the API and MCP:no native app listing	Live
Twilio (SMS, voice, numbers), Stripe, Retell	,	On the roadmap

See the roadmap for anything marked on the roadmap here.

Integration pages

Apollo + SalesCrew

Use Apollo as a data source for the SalesCrew data bank: import and enrich contacts and companies into your own Postgres project, then verify before you send.

Cal.com + SalesCrew

There is no built Cal.com connector in SalesCrew. A Cal.com webhook can still reach the inbound endpoint, and a native connector sits later on the roadmap.

Calendly + SalesCrew

Calendly bookings reach SalesCrew by webhook and become a meeting plus an inbound lead, with the booking source recorded and a reconcile job catching missed events.

Clay + SalesCrew

There is no Clay connector in SalesCrew. Push enriched rows from a Clay table into your instance with an HTTP column, or export CSV into the data bank.

GA4 + SalesCrew

A read-only GA4 collector pulls sessions and channel data into the same database as your leads and deals, so cost per lead by channel becomes a single query.

Gmail + SalesCrew

Connect a Gmail mailbox to SalesCrew over IMAP and SMTP. Threads land beside the contact record, replies are two-way, and unsubscribes write to suppression.

Google Ads + SalesCrew

A read-only Google Ads collector brings spend, clicks and campaign data next to your leads and deals. SalesCrew never changes a bid, a budget or a campaign.

Instantly + SalesCrew

SalesCrew mirrors your Instantly sender and domain registry so the pool you warmed there is visible beside the pipeline. Sending through Instantly is on the roadmap.

LinkedIn + SalesCrew

SalesCrew runs a LinkedIn queue and ledger that a person executes by hand. Nothing automates LinkedIn itself, and that limit is deliberate, not temporary.

Make + SalesCrew

There is no SalesCrew module in Make. The connection runs through outbound webhooks and the API, with signed deliveries out and scoped tokens coming in.

Meta Ads + SalesCrew

A read-only Meta Ads collector brings spend and campaign data into your own database beside leads and deals. Meta lead forms and Instagram DMs are not connected.

n8n + SalesCrew

No SalesCrew node exists in n8n. Use the Webhook node for events out and the HTTP Request node or an MCP client node for writes back into your own instance.

Outlook + SalesCrew

Connect Outlook or Microsoft 365 to SalesCrew over IMAP and SMTP. Threads join the shared inbox, replies leave from your address, and opt-outs write to suppression.

Search Console + SalesCrew

A read-only Search Console collector brings queries, pages, clicks and positions into the same database as your pipeline, with data freshness shown, not assumed.

Slack + SalesCrew

There is no customer-facing Slack integration in SalesCrew. To get CRM events into Slack today, send an outbound webhook to a Slack incoming webhook URL.

Stripe + SalesCrew

Stripe appears twice on the SalesCrew roadmap: subscription billing for SalesCrew itself, and payment links on your own Stripe key. Neither is available today.

Twilio + SalesCrew

Twilio SMS, voice and phone numbers are on the SalesCrew roadmap and are not available today. Here is what is planned, and what you can do in the meantime.

Upwork + SalesCrew

A full Upwork module in SalesCrew: saved searches, a gated job feed, proposals, outcomes and client records, so bids sit in the pipeline as a real channel.

Vapi + SalesCrew

Vapi places outbound voice calls from SalesCrew and the outcome is logged on the record. Inbound receptionist answering through Vapi is on the roadmap, not shipped.

Zapier + SalesCrew

SalesCrew connects to Zapier through outbound webhooks and its API, not a native Zapier app. Here is exactly how to wire it and what each direction can carry.