Triggers in Rewst
Last updated
Was this helpful?
Last updated
Was this helpful?
Triggers initiate workflows in Rewst. Every workflow must have a trigger to define when and how it starts. Essentially, triggers put the automate in automation. Choosing the right trigger ensures that your workflows execute at the right time, with the right data, to drive efficiency and consistency in your operations.
A trigger is also used on any form input that requires a workflow. If a form uses the Dynamic button, then you must also create a trigger on the workflow associated with that form.
Add a trigger to a workflow by clicking the Add Trigger button in the workflow builder, which will open up a new dialog with a form.
Note that you can have multiple triggers per workflow, for example a webhook and a trigger that runs when a ticket gets saved in the PSA.
Update the relevant fields in the form as needed, to set up your trigger.
Name
Whatever you would like to name your trigger, with a descriptive word or phrase for what it does.
Enabled
Toggle this on or off.
Organizations
Select all the organization that exist within Rewst that may need to use this workflow. If you add a new client, they will have to be added in that workflow trigger.
Integration Override
When a workflow is triggered by and running within the context of a child organization, by default they only have access to their own integrations and configurations— for example, the child organization's Microsoft Graph tenant. In order to give the workflow access to integrations and credentials owned by the parent organization, that default behavior must be explicitly overridden. In the above example image, the trigger allows your clients to use your PSA, RRM and Licensing integration.
Trigger Type
Form
If your trigger type is a form submission, you would select the form that links to the workflow.
Once the trigger has been created on a workflow, it can then be used on a form. This must be an options generator workflow, whose requirements can be found here.
The above is a snippet from a form where a dropdown field has been selected and the output will be based on the workflow output. When running the form, if the client is added on the trigger and the trigger is set on the form, the workflow will run, and the options will fill into the form field.
There are five key triggers to understand when getting started with Rewst. These triggers cover a range of automation scenarios, from scheduled executions to real-time event responses. In Rewst, we denote these from other triggers by calling them core triggers. Type core into the Trigger Type field to isolate most of these trigger types from the total list.
The cron job trigger initiates a workflow on a predefined schedule. This allows you to automate recurring tasks without manual intervention.
Schedules are configured using cron syntax. Consult crontab guru for help configuring this syntax.
For example, you can configure a workflow to run every Monday at 3:00 PM to generate weekly reports or clean up outdated records.
This trigger is most useful for:
Scheduled maintenance workflows (e.g., clearing stale data, running audits)
Recurring notifications (e.g., sending reminders, generating reports)
Automated check-ins (e.g., verifying system statuses, updating dashboards)
A workflow can be triggered when a user submits a form. Forms collect structured information, ensuring the workflow has the necessary data to proceed.
For example, you can submit an employee onboarding form to trigger a workflow that creates user accounts, assigns permissions, and sends welcome emails.
This trigger is most useful for:
Request-based workflows (e.g., access requests, service requests)
Intake processes (e.g., user registrations, issue reporting)
Approval workflows (e.g., leave requests, expense approvals)
For help building a form, refer to Form best practices.
For more details on forms, check out the Forms overview lesson.
A webhook trigger starts a workflow when external data is received in real time. Webhooks eliminate the need for manual checks, making them efficient for event-driven automation.
The webhook URL serves as a listening endpoint. When an external system (e.g., a CRM, ticketing system, or another Rewst workflow) sends data to the webhook URL, the workflow is triggered immediately. This enables seamless integration between Rewst and external applications without requiring a direct API connection.
For example, a webhook could trigger a workflow whenever a new customer signs up in a CRM, automatically assigning them an account manager and setting up follow-up tasks.
This trigger is most useful for:
Event-driven automation (e.g., responding to new leads, updating records on status changes)
Real-time notifications (e.g., escalating high-priority tickets, alerting teams to critical updates)
External system integrations (e.g., syncing data between platforms, processing incoming requests)
For more information on webhook triggers, refer to Use webhook triggers.
For more details on webhooks, check out the Webhooks and parameters lesson.
The always pass trigger allows a workflow to start without conditions. It is commonly used in workflows that do not depend on external events or schedules.
For example, you might use this trigger when testing workflows, executing a workflow from another workflow without needing a specific event, or populating dynamic options in a Rewst form.
This trigger is most useful for:
Manual workflow execution (e.g., running a workflow on demand)
Subworkflows or completion handlers (e.g., workflows triggered by other workflows)
Testing automation (e.g., verifying workflow functionality)
Option generators (e.g., dynamically populating form fields in Rewst)
For more information on option generators, refer to How to create, configure, and trigger an option generator workflow.
Note that this is the only common trigger type that does not start with Core, as the trigger name will be specific to your brand of PSA. Search for that in the trigger type list instead.
This trigger is similar to the webhook trigger but is specific to PSA systems. When a ticket record is saved in an integrated PSA, the workflow starts automatically. This includes both newly created tickets and updates to existing tickets.
For example, if a ticket is updated to Escalated, a workflow can trigger an alert to the appropriate team or assign a senior technician.
This trigger is most useful for:
Automating ticket management (e.g., escalating high-priority tickets, auto-assigning technicians)
SLA enforcement (e.g., sending reminders for unresolved tickets, auto-responding to specific cases)
Status-based automation (e.g., triggering follow-up workflows when a ticket is created or reaches a certain stage)
For more detailed information on PSA triggers, refer to Customize PSA ticket triggers.
When you're comfortable with the basics of triggers, learn more about trigger criteria here.
Want more practice?
There are a number of types to choose from, such as a webhook, form submission, ticket saved, M365 alerts. See for more information on common trigger types.
To modify an existing trigger, click Edit Trigger. If there are multiple triggers for the workflow, select the appropriate trigger from the dropdown menu.
While these five triggers cover the most common use cases, Rewst offers additional triggers tailored to different automation needs. Explore the available triggers in the trigger type list to find the best fit for your specific processes, and learn more about them in our additional trigger type documentation .
