Skip to main content

First steps

By following this page step by step, you create your first trigger and your first workflow, test it, then deploy it in an environment and monitor its execution. The path is intentionally minimal: each concept is detailed in its own guide, with a link.

Recommended path

If you haven't done so yet, read Concepts first to see where triggers, workflows and traces fit in.

Before you begin​

  • An Ecosystem (SaaS) platform account — your credentials are provided by your organization
  • An account with creation rights — Builder, Advanced Builder or Company Owner roles

1. Sign in​

  1. Open the Ecosystem (SaaS) platform: access is through the platform's single sign-in URL, with no URL dedicated to your company
  2. Click Sign in
  3. Enter your email and password
  4. On your first sign-in, change the temporary password received by email
OTP code (MFA)

On your first sign-in, you are prompted to register an OTP code (one-time password) in a TOTP-compatible app (e.g. Google Authenticator). If you lose access to this app, you will no longer be able to generate a code: open a support ticket to reset your MFA.

Check : the platform home page is displayed after signing in.

2. Create a trigger​

  1. Click Triggers in the menu
  2. Click Add
  3. Fill in the form and choose the simplest type to test: API route or Scheduler
  4. Click Save

The details of each field are described in Create a trigger.

Check : the trigger appears in the list with the Inactive status — this is normal, it does not trigger anything until it is associated with a workflow, activated and deployed.

3. Create the associated workflow​

  1. Click Workflows in the menu
  2. Click Add a workflow
  3. Fill in the workflow Name and select the trigger created in the previous step
  4. Click Save

The details of each field are described in Create a workflow.

Check : the editor opens with a Trigger node already present, which cannot be deleted.

4. Test the workflow​

  1. Select a workflow node in the editor (the Trigger node cannot be tested)
  2. Click Test the node
  3. Enter the trigger test data (e.g. { "orderId": "CMD-4821" }) then run the execution — the node's output context is kept to test the next node

The complete procedure is described in Test a workflow.

Check : the execution completes without error and each node displays its input and output data.

5. Deploy the trigger​

For the trigger to receive real data, you must activate it and then deploy it in an environment:

  1. Open the trigger detail page.
  2. Switch the trigger to Active.
  3. Deploy tab: select the target environment then Save.

The complete procedure is described in Deploy a trigger.

Check : the deployment appears in the trigger's Deployments tab with the Active status.

6. Deploy the workflow​

The workflow deployment is done on the same environment as the trigger (prerequisite):

  1. Open the workflow detail page.
  2. Click Deployments.
  3. Select the target environment, check the dictionary variables, then Deploy.

The complete procedure is described in Deploy a workflow.

Check : the workflow appears deployed on the environment, with the chosen version.

7. Monitor the workflow​

  1. Click Logs in the menu.
  2. Filter by workflow or trigger to follow the executions, their status and their data — see View traces.

Access to traces and their details are described in View traces.

Check : your workflow traces appear with their status (success, failure or in progress), and you can replay an execution — see Replay a trace.

What you get​

You have created a trigger, an associated workflow, tested its execution, then deployed everything in an environment. Your workflow is now monitored through traces on each execution.

Next steps​

See also: Concepts · Glossary