Overview
Not every automation starts with a change in Scrambl. Use a Scheduled trigger for time-based work, such as a Monday report task, and a Webhook trigger when another system should start the workflow.
Who can do this
- Required access: an access level that includes Workflows - Standard Access or Workflows - Full Access.
- Default access levels that include it: System Administrator.
- Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
- Neither the Team Member nor the Accountant access level includes Workflows, so by default only owners and admins see the module. Add a Workflows level to an access level to open it to others.
- Personal accounts: Not available. This is a work feature, so it is hidden in personal (family) spaces.
Owners and admins review and change access levels in Settings → Administration → Members → Access levels.
Set up a scheduled trigger
- Open the workflow in Workflows and drag Scheduled from Add nodes onto the canvas (or click the existing trigger).
- Choose the Timezone the schedule follows.
- Choose the Cadence (minutes, hours, daily, weekly, monthly, or yearly) and set Repeat Every. Minute schedules run every 10 minutes at the most.
- For weekly and monthly cadences, pick the days and time.
- Connect the actions, Save, and Activate.
Set up a webhook trigger
- Add a Webhook trigger to the canvas.
- Set the URL path. It must be unique for this workflow and becomes the end of the Endpoint URL.
- Under Shared secret, click Generate secret (or paste your own). It is required.
- Copy the Endpoint URL and the secret into the other system. It must send the secret in the
x-workflow-secretheader of every call. - Use the copyable test request under Request details to try it, then Save and Activate.
Good to know: Each webhook endpoint accepts up to 30 requests a minute. Keep the secret private; anyone with it and the URL can start the workflow.
Troubleshooting
| Issue | What to check |
|---|---|
| A scheduled workflow didn't run. | Make sure it's Active, and check the trigger's timezone and cadence. |
| Webhook calls are rejected. | The caller must send the exact secret in x-workflow-secret, and stay under 30 requests a minute. |