Trigger
What starts the automation? Examples include a form submission, new CRM stage, paid invoice, uploaded file, scheduled time or manual approval.
Inputs
List the required fields. For a lead workflow, that may include name, email, phone, service interest, source and message.
Actions
- Create or update the record.
- Assign an owner.
- Send a confirmation or internal alert.
- Schedule a follow-up.
- Log the action for review.
Failure states
Every automation needs a fallback. What happens if the email fails, the CRM API is down, a required field is missing or a duplicate record exists?
Visibility
Decide where the team sees the automation history: CRM notes, dashboard log, Slack channel, email summary or admin panel.
The goal is not invisible automation. The goal is reliable automation that people can understand when something changes.