Flow builder

The editor where you decide when a lead leaves, where it goes, and in what shape.

What it is for

A flow answers three questions: when (on every lead, or at a fixed time), what (all leads, or only those meeting a condition), and where (spreadsheet, webhook, CRM).

That is what lets you send leads from one region to one team and another region elsewhere, with no intervention.

How to use it

• A filter before the action limits what goes out. With no filter, everything goes.
• A "Code" step computes what lists cannot express: an effective date on the first day of next month, a field sent only for a couple. A short JavaScript function receives the fields and returns named fields; only the ones listed under Declared outputs reach the destinations below. It runs isolated, with no network and no require, at most 100 ms, 32 MB and 20 KB of source. Try it runs it without sending anything, on the latest contact received in the flow's scope, or on a fictional example if nothing has arrived yet. See How do I compute a field with a Code step?.
• Several actions can follow one another in the same flow: write to a spreadsheet, then call a webhook.
• The test sends for real, and not the same thing depending on the destination. Towards your own server or spreadsheet it goes out with your latest lead, without asking: the row can be deleted. Towards a partner such as OGGO Data or Nova it creates a real file, so the screen asks for confirmation and sends a fictional lead instead. Use it before switching on: a malformed webhook shows up in three seconds here, and in three days otherwise.
• The history says what went out, lead by lead, with the recipient's reply. That is where you diagnose, not in your CRM's logs.

Step by step: connecting your CRM by webhook

1. 1.Create a flow and name it after its destination, not the campaign: it will outlive the campaign.
2. 2.Choose the "Real time" trigger: it is almost always what you want. The other three ("once a day", "once a week", "once a month") batch the sends.
3. 3.Add a filter if needed. For example, only send leads from one vertical.
4. 4.Add the Webhook action and paste the address your CRM gave you.
5. 5.Set authentication if your CRM requires it. The token is encrypted on our side and never shown again.
6. 6.Run the test and read the reply. Any code from 200 to 299 counts as accepted; anything else tells you what to fix, and we keep the first 300 characters of your CRM's reply, which are often the diagnosis.
7. 7.Switch the flow on, and check the first real lead in the history.