Create a trigger

This guide lets you create a trigger and fill in its basic configuration, before activating and deploying it.

Before you begin

• Have access to an Ecosystem organization.
• Have creation rights: Builder, Advanced Builder or Company Owner roles — see Permissions — Workflows and triggers.
• Have chosen the type of trigger adapted to your need — Trigger types.

Permissions

Only the Builder, Advanced Builder and Company Owner roles can create triggers. If the Add button does not appear, contact your administrator.

Create the trigger

1. Open the creation page

1. Click Triggers in the navigation menu.
2. Click Add at the top of the page.

2. Trigger definition

Field	Required?	Description
Data source	Yes	Trigger family: API route, File, Scheduler, Polling, Google Pub/Sub event or AWS SQS. Determines the following fields and the nature of the received data. Webhooks are configured with API route.
Name	Yes	Identifies the trigger in lists and in the editor. Use a name that is meaningful for the team (e.g. « Order reception API »).
Path (slug)	Yes	Identifier of the public URL, generated from the name. Lowercase letters, digits, dots and dashes; unique within the organization. New triggers use dots as separators (e.g. api.reception.commandes).
Description	Yes	Summary of the trigger's purpose, for reviews, maintenance and handover to another team.
Type options	Depends on type	Settings specific to the chosen type (FTP server, CRON expression, SQS queue, API URL…). See the page of the corresponding type.
Tags	No	Labels to filter and find the trigger in the lists.
App	No	Business application to attach to the trigger for mapping — see Apps.

Unique path (slug)

The path must remain unique within your organization. In case of conflict, choose another identifier.

3. Save

1. Check the information entered.
2. Click Save.
3. You are redirected to the trigger detail page.

What you get

At creation, the trigger has the Inactive status: it triggers nothing. To make it operational, associate a workflow with it, then activate and deploy it in an environment.

Inactive trigger

An Inactive trigger does not run any workflow, even after deployment. Activation is a separate step from creation.

Next steps

• Manage triggers
• Deploy a trigger
• Create the associated workflow

---

See also: Introduction to triggers · Permissions — Workflows and triggers