Skip to main content
Schedules and webhooks start a Zite workflow automatically. The workflow can update your database and use connected tools, such as email or Slack.

Scheduled workflows

Tell Zite the task, timing, and timezone. For example:
Every weekday at 9am London time, email our operations team a list of overdue tasks that are still open.
Open Workflows → Schedules to review the timing. Use Edit schedule to make changes, then Publish to activate a schedule built into the app.
Schedules list with an example daily report and controls to run, edit, or remove its schedule

Review the next run and publish any pending schedule changes.

Creating schedules requires Business, Team, or Enterprise. Existing schedules keep running if you downgrade, but you can’t create new ones.
Follow Scheduled Workflows for setup, timezones, and reminders created by app users.

Webhooks

Use a webhook when the source tool can send an event directly to Zite. For example:
When my form tool sends a new enquiry, save its name, email, and message in the Enquiries table. Don’t create another record if the same submission arrives twice.
  1. Ask Zite in the chat, or open Workflows → Webhooks → Add webhook.
  2. Copy the Test URL Zite provides into the source tool’s webhook settings.
  3. Send a sample event and select Use selected event.
  4. Review the workflow, Publish, and send another event to check the result.
Webhooks list with an illustrative enquiry webhook and its inbound address concealed

Manage incoming events in Workflows → Webhooks. Keep the address private.

Webhooks are available on all plans. See Webhooks for connecting a source tool, pausing events, and troubleshooting.

Check the result

Open the workflow, then History. Check the trigger, status, and result of each run. A successful delivery from the source tool doesn’t by itself confirm the intended record was saved.
Example workflow history with successful and failed webhook runs

Open a failed run to find the step that needs attention.

Testing can change real records or send messages. Use sample data and check the result before retrying. Published executions use your workflow-run allowance.
Last modified on October 22, 2026