Create automation
Objective
Configure a new automation rule that fires when a system action occurs and sends a request to the configured webhook.
Before starting
- Have
AUTOMATIONS: WRITE. - Have the destination webhook URL, validated and with CORS permissions if applicable.
- Define the action key and the associated service.
- Have clear the subset of fields that will be sent in the payload.
Step by step
- Enter the Automations module from the side menu.
- Click New automation.
- The creation dialog opens. Enter:
- Rule name.
- Action key (system actions selector).
- Webhook URL (destination endpoint).
- Service (services catalog selector, if applicable).
- Selected fields (subset of event fields).
- Status (active or inactive).
- Confirm with Save.
Expected result
- The rule is registered.
- If it is active, it will fire every time the action key is executed.
- The system shows a success message.
Pending: add screenshot of
automatizaciones-crear-01-dialogo.png.
Common errors
| Situation | What to do |
|---|---|
| The URL does not respond | Validate the endpoint and permissions before activating the rule. |
| The action key does not appear | Verify that the system action is active. |
| The rule does not fire | Verify that the rule is active and that the action is being executed in the system. |
Suggested permissions
AUTOMATIONS: WRITE.
Operational recommendations
- Validate the webhook in a test environment before activating in production.
- Document the URL, its purpose and the responsible person for the endpoint.
- Limit the selected fields to what is strictly necessary.
Relation with other modules
- Notifications: rules can work together with the notification system.
- Services: the service selector takes the values from the catalog.
- Audit log: the firings are recorded.