Setting Up Triggers in Flow Studio

Triggers are the starting point for any flow in Flow Studio. They define the event that initiates your workflow and connect Flow Studio to external apps or services through webhooks or API calls. Setting up triggers is a key step to building effective automations.

What Is a Trigger?

A trigger is an event or condition that starts a workflow. It can range from receiving a new email, updating a database record, or calling an API. In Flow Studio, triggers connect to external systems through endpoints to receive or send data.

Steps to Set Up a Trigger

1. Navigate to the Triggers Section Open Flow Studio and click on Triggers node.

1. Use the Public Route In the Triggers section, you’ll see the Public Route (Authentication in URL). This is the unique endpoint assigned for each webhook you call. Ensure to copy and paste the full URL of the API key when configuring your trigger.

   [Insert image of Public Route configuration]

2. Select the Trigger Type Depending on the app or service you’re connecting, select the appropriate HTTP method for your trigger. Flow Studio supports the following trigger types:

   • GET

   • POST

   • PUT

   • PATCH

   • DELETE

---

What Each Trigger Type Means

1. GET

   • Retrieves data from a specified resource.

   • Example: Use GET to fetch a list of users or retrieve data from an external API.

2. POST

   • Sends data to create a new resource.

   • Example: Use POST to add a new record to a database or submit a form.

3. PUT

   • Updates or replaces an existing resource.

   • Example: Use PUT to modify the details of an existing user in a database.

4. PATCH

   • Partially updates an existing resource.

   • Example: Use PATCH to update only a specific field, such as changing a user’s email address.

5. DELETE

   • Removes a resource from the system.

   • Example: Use DELETE to remove a user or delete a record from a database.

---

Best Practices for Using Triggers

• Test Your Endpoint: Ensure that the endpoint URL is correct and functional by testing it before finalizing your flow.

• Understand API Documentation: Review the API developer's documentation to determine the required HTTP method (GET, POST, etc.) and the expected parameters.

• Secure Your Public Route: Avoid exposing your API key publicly by following recommended security practices, such as IP whitelisting or encryption.

---

1. Enable your public route using the toggle.

1. Click the icon next to the flow name to get your full authentication URL.

With this URL you have set up your first trigger and have created your first endpoint to send the info you need according to each.