Integrations

Overview

The Integrations page connects SalesFlow to the tools around it. Each integration shows a status badge so you can see at a glance whether it is connected, and usage statistics where relevant.

Gmail

1. 1Open Integrations and choose to connect Google.
2. 2Sign in to the Google account you want to send from and grant access.
3. 3The card switches to connected, and email actions across the app start using that account.

Usage statistics show how many emails were sent today, this month and in total. Your plan sets a monthly email allowance.

Twilio Voice

With Twilio connected, the call button on a contact dials from your browser. There is a test action on the integration card to confirm the configuration works before you rely on it.

• Place calls to contacts without leaving the app.
• Track call status while the call is in progress.
• Keep call recordings against the contact.
• See calls made today and in total on the integration card.

External database sync

If you keep a system of record outside the CRM, this integration writes deal data into a MySQL table you nominate. You choose when it fires — either only when a deal is won, or on every deal update — and you map each column in your table to a field on the deal.

A test action verifies the connection and the mapping before you enable it.

API calls on won deals

Set up any number of API calls that fire automatically when one of your deals moves into a won stage. Each call is a POST request with its own endpoint, headers and JSON body, so you can notify a billing system, an order pipeline and a chat relay from the same event.

1. 1Open Integrations and configure API calls on won deals.
2. 2Add a call and give it a name so you can recognise it later.
3. 3Enter the https endpoint URL it should POST to.
4. 4Add any headers the receiver needs, such as an Authorization token.
5. 5Write the JSON body, using placeholders for deal and contact values.
6. 6Send a test delivery to confirm the receiver accepts it, then save.

Placeholders

Anything in double braces is replaced with a value from the won deal or its contact. A placeholder inside quotes becomes text; one on its own becomes a number, so amounts stay numeric.

{
  "customer": "{{contact.name}}",
  "email": "{{contact.email}}",
  "deal": "{{deal.title}}",
  "amount": {{deal.value}}
}

Available placeholders are deal.id, deal.title, deal.value, deal.stage, deal.probability, deal.description, deal.comment, deal.openDate, deal.closeDate, contact.name, contact.email, contact.phone and contact.company. Use deal.id to send the CRM's own identifier for the won deal, so the receiving system can match it back later.

Delivery

• Every enabled call fires at the same time when a deal reaches a won stage.
• Content-Type is set to application/json for you.
• A call that times out after 10 seconds, or returns 429 or a 5xx, is retried twice with a short pause.
• Other error responses are not retried, since repeating them would not help.
• Failures do not block or undo the deal update.

Website lead capture

Your website can post form submissions straight into Contacts. The Integrations page gives you the endpoint, your form secret and a ready-to-run example, and the API reference documents the request in full.

• Submissions create a new contact, or attach an enquiry to the matching existing contact.
• Campaign details such as UTM parameters, the page title and the form title are captured alongside the lead.
• Including a project slug routes the lead to that project's assignees.
• Team members are notified when a lead arrives.

AI calling

AI calling places automated calls to leads with live transcription and scoring, and reports on the outcome. It is part of the top plan; some capabilities are marked as coming soon in the interface while they are being finished.