What happens after submitting

A record is created on every accepted submission. What happens on top is a list on the right of the builder: put into a stage, send a confirmation, notify the team, start a distribution, call another system. Each entry can be switched off on its own.

The record is always created

It does not depend on any of the actions. Switch them all off and you still get a record, only without a confirmation, without a stage and without a notification. The reverse does not hold: if an action fails, the record stays. A full mailbox must not cost you an enquiry.

Five outputs, in the order of the list

Put into a stage decides where the record is created on the board, not where it moves afterwards. The confirmation goes to the address from the form and uses the same templates as an automation. The notification goes inwards, to a person or a role. The distribution hands the record to partners. The call to another system sends the record as a message to an address of your choosing.

Outputs exist only for booked modules

Stage and distribution belong to other modules. If one of them is not booked, the builder does not offer the output at all. If it was set up before the module was cancelled, it stays saved, is skipped on submission and works again once the module is booked. The record is still created, and the submission log says what was skipped. That way a form delivers no work nobody pays for and loses no lead.

First the record, then the confirmation, the automation last

The order is a promise to the sender. Their confirmation is out before an automation starts working. The other way round, the mail would hang behind a chain somebody built three months ago. Attached files reach the record before the confirmation, so a sentence like we have received your documents is true when it goes out.

Whatever did not work is in the submission

Every submission carries a result per output: ran, skipped or failed, with a reason. If you want to know why a confirmation never arrived, you look there and not in a mailbox. A failed output does not stop the others.

Step by step

1. In the builder, click Form on the right when no field is selected.
2. Switch on the output you want under After submitting.
3. Open the entry and set what it needs: stage, template, recipient or address.
4. Save and submit the form once yourself.
5. Check under Records that the record is where it belongs.

The confirmation does not arrive.

Check in the submission whether the output ran. Skipped means an entry or a module is missing; failed names the reason in the row. The most common case is a form without an email field.

Can one form put records into several stages?

No, one stage per form. To branch on an answer, use an automation with a condition; the form only decides where the record is created.

Why is an output missing?

It belongs to a module this account has not booked, such as distribution. The builder then does not offer it. An entry set up earlier stays saved and works again once the module is booked.

How do I start an automation from a form?

Not by hand. Every submission fires a trigger of its own that an automation can wait for, optionally for one particular form.

What is in the message to another system?

The record with its fields, the same shape the API returns. You set the address and the headers on the entry.