Chain Autopilot gives you full control over how and when automated actions happen on your loads. While rule templates are a fast way to get started, many teams eventually need something more tailored, whether that means adding a filter to a rule, adjusting when it runs, or building a workflow from scratch.
This guide covers how to:
Edit an existing Autopilot rule template
Create a brand new rule
Understand the role of triggers, conditions, and actions
Decide when to use templates vs. build from scratch
1. Editing an Existing Rule Template
Most users start with a prebuilt rule template. But templates are flexible, you can modify them at any time.
To edit:
Navigate to Autopilot settings
Find an existing rule under Your Rules
Click the three-dot menu (⋮) on the rule card
Select Edit Rule
This will open the rule in the builder interface, where you can:
Change the trigger (when the rule should evaluate)
Add or remove conditions (logic filters)
Modify the action (what the rule does)
Example: You’re using a “2 hours before ETA” reminder, but you want it to fire only if tracking is off. Just edit the rule and add a condition.
2. Creating a Custom Rule from Scratch
Sometimes a template won’t cut it. You may want a rule for a specific customer, trailer type, or tracking scenario. That’s where custom rules come in.
To create one:
Go to Autopilot settings
Click “Create a new rule”
You’ll see a blank configuration form with the following fields:
Name & Description – Describe what this rule does
Tags – Add labels to organize and search rules later
Type of Rule – Usually “Shipment”
Trigger – When the rule should run (more on this below)
Conditions – Optional filters that must be true for the rule to proceed
Actions – What the rule should do if conditions are met
You’re building a simple logic flow:
“At this time → if these things are true → do this thing.”
4. When to Use a Template vs. Create a Custom Rule
Use a template when… | Create a custom rule when… |
You want to automate a common milestone like check calls, POD requests, or ETA reminders | You want to handle a specific customer, load type, or tracking condition |
You’re new to Autopilot and want to get started quickly | You need multi-step logic or more precise targeting |
You want something “good enough” out of the box | You’re building a scalable ops playbook tailored to your team |
5. What Happens Next?
Once the trigger fires, Autopilot evaluates the conditions you’ve defined. If they pass, it then performs the action (such as sending a message or updating a status).
You can learn more about those steps here: