Form Automations

React automatically when someone completes a form — notify the team, email a contact, or

log a follow-up.

## Triggers

| Trigger | Type | Fires when |

|---|---|---|

| **Form Completion** | Event | A form is completed/submitted. |

Form completions are usually linked to a project or quote, so those records' details are

available to the actions (for example, in email placeholders).

## Conditions you can use

- Fields on the completed form and its linked record, so you can react only to specific

  forms or answers.

## Actions

A form completion can trigger several actions. The form-specific one is:

**Send Form Completion Email** — emails a contact about the completed form.

- *To* / *CC* — recipients (Project Manager, Project Client/Contact, Billing Contact, or a

  typed address). *To* is **required**.

- *Subject* and *Message* — **required**; supports form and linked-record placeholders.

Because a form completion links to its project, you can also use project actions on this

trigger:

- **Send Project Chat Message** — post the submission into the project's chat channel.

- **Notify the Project Manager** — send an in-app notification.

- **Create To-Do** — log a follow-up to-do.

## Notes

There are no pre-built Library templates for forms yet — build your own from the trigger

and actions above (*Workflows → Add Workflow*).

Typical custom workflows:

- **Alert the team when a form is submitted** — *Form Completion* → *Send Project Chat

  Message* or *Notify the Project Manager*.

- **Email a confirmation** — *Form Completion* → *Send Form Completion Email* to the client

  or contact.

- **Create a follow-up** — *Form Completion* → *Create To-Do* for the project manager.

## Tips

- The Send Form Completion Email action doesn't attach a generated document — it's for a

  message, not a PDF hand-off. Use a project email action if you need to attach a generated

  document.