Before you start
- Applies to
- Web app
- Access
- Owner or Admin with automation access
- Connection
- Internet connection required
- Time
- About 10 minutes for a simple rule
You'll need
- A specific event that should start the workflow
- A clear recipient or task owner
- A test record that can trigger the rule without affecting live work
Steps
Write the rule in one sentence
Use the pattern: When this event happens, and these conditions are true, do this action. If the sentence contains several unrelated outcomes, create separate automations so each one is easier to test and maintain.
Choose Add automation
Open Automations and choose Add automation. MapTrack creates an Untitled automation in Draft state immediately, so rename and finish it before leaving the builder.
Configure the Trigger
Under Trigger, choose the event source and action that should start the automation. Use the narrowest event that matches the workflow.
Add a Condition only when needed
A rule without conditions runs for every matching trigger. Add conditions when the automation should run only for a particular answer, status, category or other supported value.
Set the Schedule
The default is to run once for each event, immediately. Add a delay or repeat only when the operational timing requires it.
Add the Action
Choose what MapTrack should do. Current enabled actions are Alert / Notification, which sends email, and Create task. Webhook appears in the action list but cannot be selected when creating or editing an automation.
Save and test safely
Use Save as Draft while checking the rule. When it is ready, choose Save & Activate, trigger it with a controlled test record and check both the automation History and the resulting email or task.
What you should see
The automation is Active, a controlled event appears in its History and the expected email alert or task is created once.
Current limits
- Current notification actions send email. Do not plan on push, Slack or Teams delivery.
- Webhook cannot be selected in the current action picker and must not be used as a rollout dependency.
- Automations are server-side and require a network connection.
Troubleshooting
| What you see | Likely cause | What to do |
|---|---|---|
| What you seeNothing happens after the test event | Likely causeThe automation is still a draft, the trigger does not match or a condition is false. | What to doCheck the Active state, read the Trigger and Condition in order, then use a controlled record that matches every value. |
| What you seeThe email alert does not arrive | Likely causeThe selected Person record is missing, archived, deleted or has no valid email address, the trigger or condition did not match, the action failed or delivery was filtered. | What to doOpen the automation History and inspect the action status. Confirm the selected Person has not been archived or deleted and their email address is correct, then check filtered mail. If the action failed, contact support with the automation name, run time and displayed status. |
| What you seeThe automation runs too often | Likely causeThe trigger is broad or the rule has no limiting condition. | What to doDeactivate it, add a specific condition or schedule and test again before reactivating. |
Common questions
Still stuck?
Tell us the step you reached, what you expected and the exact message on screen. Remove customer, asset and personal details before sharing a screenshot.