Launchers let users create new, trackable work directly from a Record or Action Type. They pull information already in view—like field values, linked records, or ownership—to pre‑fill and connect the new Action or Record. This lets users capture follow‑ups or next steps without switching screens or re‑entering data. Depending on configuration, a launcher can also prompt the user to add notes, making it ideal for quickly recording action items from a meeting or call.
Launchers strengthen continuity between planning and doing. They are most commonly used in meeting, project, and process Action Types where next steps or assignments are identified in real time.
They help your team:
Whether you are tracking client meetings, internal reviews, or cross‑department projects, Launchers embed execution directly into context.
| YAML KEY | DESCRIPTION |
|---|---|
| control_type | Defines the field as a Launcher control. |
| label | The visible text label shown on the Launch button. |
| job_create_on | Specifies the action triggered when the Launcher is clicked (what type of record is created, e.g. “Create Job”). |
| job_info | Defines how the new Action or Job is created, including type ID, assigned_user, owner_user, due‑date rules, and any pre‑filled fields. |
| props.description (optional) | Provides a text description or tooltip for the Launcher’s purpose. |
Launchers are often implemented in meeting templates.
For example, a Meeting Agenda Action Type might include a section for attendees, topics, and decisions, followed by a Launcher labeled “Create Action Item.”