Automations
Item to Form ships three custom blocks for monday.com's automation builder: two triggers that react to form lifecycle events, and one action that creates a form from a reusable settings template. Combine them with monday's built-in blocks to send forms automatically and react to submissions across your workflows.
Overview
Each block is registered in the Item to Form app manifest and appears in the monday.com recipe builder once the app is installed on your account. There are two trigger blocks and one action block:
When form is created
Fires every time a new Item to Form form is generated on a board — whether the form was created manually, from the Multi-Item view, from the public API, or from another automation.
When form is submitted
Fires every time an Item to Form form is successfully submitted and applied to monday.com — including submissions that were queued and processed asynchronously.
Send form using settings
Creates an Item to Form form on the item that flowed into the action. The columns, settings, and delivery method come from a Settings Template you configure in the Item to Form app.
Trigger: When form is created
Use this trigger to react whenever a new form is generated. Item to Form dispatches the event as soon as the form is persisted, so downstream blocks see the form URL immediately.
Inputs
| Field | Type | Description |
|---|---|---|
| board | Board (optional) | Defaults to the recipe's current board. Leave it alone unless you want the trigger to fire only for a specific board. |
Outputs
These output fields are available to downstream blocks in the recipe:
| Field | Type | Description |
|---|---|---|
| Form Type | Text | Form source: item for item-bound forms, board for permanent board-backed links, or one_time for single-use board links. |
| Item | Item | The monday.com item the form is bound to. Omitted for one-time board-backed forms (no item exists yet). |
| Board | Board | The board the form was created on. |
| Form URL | Text | The public, signed URL recipients use to fill the form. |
Trigger: When form is submitted
Use this trigger to react after a form submission has been durably applied to monday.com. It fires both on the immediate post-commit path and when a previously queued submission transitions to success during async processing.
Inputs and outputs
This trigger exposes the same inbound and outbound fields as the When form is created trigger: an optional board input to scope the recipe, and Form Type, Item, Board, and Form URL outputs. For one-time board-backed forms, the newly created item is available as the Item output.
Action: Send form using settings
This action generates a form on the item that flowed into the recipe, using a Settings Template you configure in advance in the Item to Form app. It's the building block for recipes like "When a status changes to X, send the form to this item."
Inputs
| Field | Source | Description |
|---|---|---|
| boardId | Recipe context | Automatically populated from the board the recipe lives on. |
| Item | Trigger output | The item the form will be created for. Map this from the trigger that precedes the action (for example, the item that just changed status). |
| Settings template | Dropdown | Pick a template you created in Settings → Templates. A built-in Default (all fields via link) option is always available even when you have no custom templates yet. |
What happens at runtime
- Item to Form loads the chosen settings template and validates that the template's selected columns still exist on the board.
- Item to Form uses the template creator's stored monday.com OAuth token to talk to the monday API — so the user who built the template must remain authorized in the app.
- If the template uses email delivery, Item to Form reads the recipient's address from the configured column on the triggering item. An empty email column degrades gracefully to a link-only form for that item.
- The form is generated and a unique link is created. The When form is created trigger fires immediately, so you can chain another recipe to it.
- If the form's email delivery is enabled, the recipient receives the link via email — including any reminders the template configures.
Settings templates
A settings template is a reusable bundle that captures everything the Send form using settings action needs to know about a form: which board, which columns, the form settings, and how the form should be delivered. Templates are scoped per account and named per board.
Creating a template
Open the Item to Form app, navigate to Settings → Templates, and click Create Template. The wizard walks through five steps:
| Step | What you configure |
|---|---|
| Board | The monday.com board the template applies to. Templates are board-scoped so column ids stay stable. |
| Columns | Which board columns appear as fields on the generated form. Same column-type support as a manually generated form — see Supported Field Types. |
| Settings | Form-level options such as title, custom message, password protection, notify-on-submit, allow editing after submit, and expiration. See Form Settings. |
| Delivery | Either link (recipient gets a link via your own channels) or email (Item to Form sends an email using a chosen email template and pulls the recipient address from a board column). |
| Name | A human-readable name unique per board. This is what appears in the recipe builder dropdown. |
Recipe examples
A few common ways to combine Item to Form blocks with monday's built-in trigger and action library:
Auto-send a form when an item is created
When an item is created → Send form using these Settings. Map the trigger's item to the action and pick the template that drives onboarding for that board.
Resend a form when status changes
When status changes to "Needs info" → Send form using these Settings. Pair with an email-delivery template that points at the requester's email column to ping them automatically.
Notify a channel when a submission lands
When form is submitted → monday's built-in Notify someone action. Use the Form URL and Item outputs in the message body for quick links back to the source.
Track form generation in another board
When form is created → monday's built-in Create item action on a tracking board. Persist Form Type, Item, and Form URL as a lightweight audit trail.