Flows (automation)

Flows automate work in Loop. A flow watches for a trigger, such as a form submission, and then runs one or more actions, such as adding the person to your Pulse CRM or sending them an email. This saves manual data entry and makes sure no lead is missed.

How a flow works

A flow is built on a canvas as a small diagram:

1. A trigger starts the flow, for example when a capture form is submitted.
2. One or more actions run in response, for example Add to Pulse to create a contact, or Send Email to follow up.
3. You map the incoming fields (such as name, email, company) into each action so the data lands in the right place. A smart suggester helps match fields for you.

Triggers

A trigger is the event that starts a flow. You can choose:

• A capture form is submitted. The flow runs whenever someone submits a standalone public capture form. You pick the form to listen to.
• A campaign form is submitted. The flow runs when someone submits a form that is linked to a specific campaign. You pick the campaign first, then the form within it.

Actions and node types

After the trigger, you add one or more steps. The available node types are:

Add to Pulse

Creates a contact (and company) in your Pulse CRM from the submission. You map the form fields to the contact fields so the right values land in the right place.

Enrich with AI

Automatically enriches the contact created by an earlier Add to Pulse step with extra details. This node needs an Add to Pulse step before it in the flow, and it inherits the contact from that step, so there is nothing to map.

Send Email

Sends an email as part of the flow, for example a thank-you or follow-up message to the person who submitted the form.

Send WhatsApp

Sends a WhatsApp message using an approved WhatsApp template.

Condition

Branches the flow based on a field value, so different steps run depending on what the data contains.

Delay

Waits a set amount of time before continuing to the next step. You choose the amount in minutes, hours, or days. This is useful for spacing out follow-ups.

Premium nodes

Some node types may be available only on higher plans. A locked node shows a premium badge in the builder, and selecting it prompts you to upgrade. See Plans, seats & billing.

Field mapping

Each action takes its values from field mapping. You can map fields from the form that triggered the flow, and you can also map the outputs of upstream steps (for example, details produced by an earlier Add to Pulse or Enrich with AI step) into a later action. A smart suggester helps match fields for you.

Build a flow

1. Open Flows from the menu to see your automations and how many are active.
2. Choose New Flow to open the builder.
3. Set the trigger and choose the form (or campaign and form) to listen to.
4. Add one or more actions and map their fields.
5. Assign an owner using the search box (the owner is the user the created records belong to).

Use the full-screen view of the builder for more room, and the Save button there to keep changes as you work.

Save, Verify, and Activate

• Save keeps your progress at any time, even if the flow is not yet complete. A saved draft is not running.
• Verify checks that the flow is valid (its layout, field mappings, and node prerequisites) without turning it on. Use this to catch problems early.
• Activate runs the same checks and turns the flow on so it runs on new submissions. Only active flows run, and Loop will point out anything missing before it activates.

Auto-pause (self-protection)

Loop protects your flows so they never run with broken mappings:

• If you edit a linked form in a way that breaks a flow's field mapping, Loop automatically pauses the affected flow and flags it for review. Fix the mapping, then activate it again.
• If a flow fails repeatedly when it runs, Loop can also auto-pause it so it stops retrying a broken step.

A paused flow shows a note explaining why, so you know what to review.

Monitor

The Execution logs show every run with its time, status, and result, including success or failure for each step. Filter by flow, date, or status (succeeded, failed, running), and open a run to see the data it received and the steps it ran. This is the first place to look if something does not behave as expected. Logs are kept even after a flow is archived, so your run history is never lost.

Plan limits

Your plan sets how many flows can be active at once. If flows are not included, the feature is locked. As you approach the limit, Loop warns you. See Plans, seats & billing.

Example: capture leads automatically

1. Build a Capture form for your event.
2. Create a flow with the trigger A capture form is submitted, pointing at that form.
3. Add the action Add to Pulse and map the fields.
4. Add a Send Email step to thank the person, mapping their email from the form.
5. Use Verify to confirm the flow is valid, then Activate it.
6. As entries arrive, new contacts appear in Pulse automatically and the email goes out. Check the execution logs to confirm.