Routing capture form submissions to a workflow or board

Lead forms (Contacts & CRM → Forms) capture contacts straight into your workspace from your website. Every submission creates a contact and, if you configure it, a deal on the Pipeline too — and both events can trigger your Automations (Workflows), so an incoming lead doesn't have to wait for someone to check it by hand.

Requirements

• CRM permission to create/edit Lead forms
• At least one Pipeline set up in the workspace (if you want deals created)

Steps

1. Go to Contacts & CRM → Lead forms and create a new one (or open an existing one).
2. Add the form's fields and map them to contact data (Name, Email, Phone, Company, Job title, City, Country, or a Custom field).
3. In the On lead received section, turn on Create a deal on the pipeline and pick the target Pipeline (if you don't pick one, it falls back to the workspace's default pipeline).
4. Add Tags to apply to the contact if you want to segment it or trigger a workflow off that tag.
5. Save and copy the embed code (iframe) or the public link to share it.

Connecting it to a workflow

Every submission creates a contact — that fires the Contact created event in Automations. If you turned on deal creation, it also fires Record created for that deal. Build a workflow off those triggers to, say, notify the sales team, or use a node to create a card on a Projects board straight from the deal.

Example

A "Contact us" form on your landing page creates the contact and a deal on the "Web Sales" Pipeline. A workflow triggered by "Record created" automatically assigns that deal to a rep and creates a card on the "Incoming leads" Projects board, so the team sees it without opening the CRM.

Tips

• Leave Anti-spam minimum time and the hidden bot-trap field on — they're already set up to filter automated submissions.
• Use Redirect to a URL to send the visitor to your own thank-you page instead of the default message.

Troubleshooting

If the form isn't creating deals, check that Create a deal on the pipeline is still on and that the chosen Pipeline hasn't been deleted — if the configured pipeline no longer exists, the deal falls back to the workspace's default pipeline.