Triggers

Introduction

A trigger is the entry point of every Flow. To use a FactBranch Flow as a webhook for one of your external services, you create a Flow that's triggered when you send a POST request to our API endpoint. Or - if you are using one of our apps - a Flow can be triggered when the app is opened in Zendesk, Gmail or one of the other services we have apps for.

In this article you'll learn about:

How to capture incoming requests

After you create a Flow, it's a great idea to capture some real-world data that you can use to test querying your data sources and generating outputs.

In the Flow dashboard select the Flow you'd like to record data for.

Click on Config next to the trigger block to open the trigger config page.

In the Incoming data box activate Record requests.

Capturing an incoming request from an app

If you've installed one of our apps, open the place where you've installed the app. In Zendesk Support this might be a ticket or in Zendesk Sell a deal or a lead, in Gmail an email conversation, etc. Make sure the FactBranch app is loaded and visible. The FactBranch app should not display any errors. If it does and you're unsure what to do, please do reach out to support@factbranch.com anytime.

Capturing an incoming request from a webhook

If the trigger type is a webhook, follow the directions on the trigger config page to set up the webhook and post data to the endpoint at FactBranch using the Bearer token from the trigger config page.

Using the request data as test data

Head back to the trigger config page in FactBranch and click reload. You should see at least one request in the list of Incoming data.

Click on a recorded request to reveal its content. To use that particular data as incoming data for this Flow, click on Use as test data. The trigger's test data below will update.

Don't forget to deactivate Record requests again once you're finished collecting test data.

You can now set up the rest of the Flow by configuring existing nodes or adding more nodes to the Flow.