Every time an experience is created, it requires a way to start. This is called a trigger which is the first node in every experience. There are four categories of triggers:
Every furl experience is initially created with a Manual Trigger. This means that the experience will only start when you manually run an experience from the furl app. Many automated processes are intended to be run based on a recurring interval, external event, or a change in state from another tool. This is when you change the trigger to one that better suits your needs.
A webhook trigger allows you to start an experience by sending a POST request to a webhook URL. This is useful when you want to start an experience from a third-party service or tool. For example, you can start an experience when a new user signs up for your product or when a new order is placed.
Once the webhook trigger is selected, a webhook url is be created. This url then can be used to send a request to start an experience.
While this trigger type is certainly most useful for a more technical audience, we’ve provided multiple examples of running a webhook trigger (curl, powershell, and generic details).
A schedule trigger allows you to start an experience at a specific time throughout the week. This is useful when you want to run an experience on a recurring basis. For example, you can start an experience every Monday at 9am to ask your team for standup updates or every day at 5pm to communicate all the product releases for the day.
It is important to remember, if there are any experience inputs that are required they must be configured when setting up the schedule. For example, if you have an experience that asks for a message to send on discord, you must configure the schedule to provide the message. If you do not, the experience cannot be enabled.
Automated triggers are based on events or changes in a third-party tool. More documentation for this trigger type will come soon.