Automations
Automations are integrations with complex data flow, which can have the following triggers:
- By Event / Webhook
- Email
- Scheduling
Integrations have a detailed log that must be configured at design time. All log data has a configurable expiration time in the
Retention period, in days field, which can range from 0 to 30 days.This trigger is intended for integrations that will be initiated on-demand through external events. When selecting this type of trigger, a unique URL will be generated per environment to be configured in the event source. There are the following authentication options:
Option | Description |
|---|---|
No authentication | The webhook allows it to be called by anyone who has the URL |
Basic Authentication | To trigger the webhook, you will need to send a username and password |
Parameter in URL | To trigger the webhook, you will need to send a specific parameter in the URL |
Value in header | To trigger the webhook it will be necessary to send specific header defined by you |
At the foot of the triggers page, there are sample code snippets in HTTP, Javascript, Curl, C#, Go, Java, and Python.
This trigger is intended for integrations that will be launched on-demand via email. The mailbox address is automatically generated and must be unique among all customers. The entire flow will be controlled by the SNS.
This trigger is intended for integrations that will be initiated through a schedule controlled by the platform itself. There are a number of combinations available between hours, days, weeks, months, and years. It should be noted that if the option
day, every hour, every minute the integration will be executed once per minute.In this section, the entire history of deployments of integration is available, with the responsible user and date and time of deployment. For transport between environments, there is the
Transport button, which generates a transport request containing the automation, package, and all assigned systems, along with the parameters previously registered. This request must be approved in the target system to be effective.It is possible to register dynamic parameters that will be available during execution. It is generally used to keep in parameters data that can change according to the environment or are frequently modified to avoid changes in the source code.
The platform has the ability to send automatic notifications in case of an error. To do this, just click on
+ Add and set the notification address and language. The email sent will not contain the logs themselves for security reasons but will send a direct link to the log with the error in question.There is the possibility of creating limited users that are generally not part of your organization. These users will only have access to the automation log if it is allowed in this section. Just enable or disable.
For the data of a system to be available in the execution environment, it must be assigned to automation. In the case of transport, the assigned systems will also be transported.
Last modified 5mo ago