Install and customize a recommended automation

Copy a system workflow into your org, review trigger templates, publish, and test it.

Recommended Automations are GTM Engine's starting points for common workflow patterns. Installing one copies the system workflow into your org so you can review, customize, publish, and run it like any other workflow.

What You'll Build

You will install a recommended automation, review any bundled trigger templates, publish the workflow, and confirm it runs correctly in your org.

When to Use This

Use a recommended automation when:

You want a proven starting point instead of a blank workflow.
The automation is close to your desired process but needs org-specific fields, stages, or prompt wording.
You want to learn how a system workflow is structured.
You need a reusable workflow that can later be exposed as an agent tool.

Estimated time: 15-30 minutes.

Concepts used: Automation Library, Workflows, Triggers, Variables.

Prerequisites

Admin access to Automation.
Connected CRM or built-in GTM Engine CRM records.
Any required integrations for the automation, such as enrichment, Slack, email, or Instantly.

1. Open Recommended Automations

Go to Automation → Recommended Automations from the Automation Library.

Browse by category and open the card for the automation you want to install. Review:

What the workflow does.
Which record types it touches.
Whether it ships with default trigger templates.
Which integrations or fields it expects.

2. Add the Automation

Click Add Automation.

GTM Engine copies the system workflow into your org and opens it in the workflow builder. It becomes your copy, so you can edit it without changing the original system version.

If the automation includes default trigger templates, the install flow shows them before copying.

3. Review Trigger Templates

Trigger templates may include org-specific values, such as:

Pipeline stage names.
Enum values.
Field names.
Record type filters.

Review highlighted values before installing. If a trigger should fire when an opportunity reaches Qualified, make sure that stage exists in your org and points to the right pipeline stage.

4. Review Inputs, Outputs, and Variables

After install, open the Triggers / Inputs / Outputs panel.

Check:

Required inputs are declared clearly.
Outputs are named and useful.
Trigger assignments map trigger outputs into workflow inputs.
Variables in task configs point to existing inputs.* or steps.* values.

Open Diagnostics before publishing. Fix unresolved variables or schema errors first.

5. Customize the Workflow

Make the smallest changes needed for your org:

Update prompts to match your team's language.
Map Update Record tasks to your fields.
Change trigger filters to your stages or enum values.
Remove tasks tied to integrations you do not use.
Add tags or folder:<name> tags so the automation appears in the right folder.

Avoid changing too much at once. Install, test, and then iterate.

6. Publish and Test

Click Publish when the workflow is ready.

Then test from the safest entry point:

Use a manual run from the builder for workflows with side effects.
Use the trigger's Test action for trigger-driven workflows.
Use a record page run action when the workflow is record-specific.

Inspect the run in the Runs tab and confirm each step received the expected inputs.

Success Check

You are done when:

The recommended automation appears in your workflow library.
Any trigger templates are copied and assigned correctly.
Diagnostics are clean.
The workflow is published.
A test run completes with expected outputs or record updates.

Common Pitfalls

Publishing before reviewing highlighted stage or enum values.
Forgetting that trigger templates are copied into your org and can be edited.
Leaving integration tasks enabled when your org does not have the integration connected.
Editing the workflow input contract without updating trigger mappings.
Treating a recommended automation as finished without testing it on your data.