Templates
Start from something that already works
Each of these imports as a real, editable workflow. The ones marked no setup run immediately — nothing to connect and no credentials to find.
-
webhook
set vars
condition
set vars ×2
Your first workflow
A working example you can run right now: it takes an incoming order, tidies up the values, and routes big orders differently from small ones. No accounts to connect — press Test on any step to watch real data flow through it.
-
webhook
approval
email ×2
Ask a person before it happens
Pause the workflow and email someone an approve/reject link — the run waits for their decision, then takes a different path depending on the answer. Useful for refunds, discounts, or anything that shouldn't happen unattended.
-
webhook
digest
Collect events for a daily digest
Instead of an email per event, quietly collect each one. Pair this with “Send the daily digest”, which empties the pile on a schedule and sends a single summary.
-
schedule
digest
condition
email
Send the daily digest
Once a day, empty everything collected by “Collect events for a daily digest” and send it as one email — and stay quiet on days when nothing happened.
-
webhook
storage
condition
storage
set vars
Ignore duplicate events
Some systems send the same event twice. This remembers the last id it handled and skips anything it has already seen, so the work only happens once.
-
webhook
switch
email
digest
set vars
Send urgent things down a different path
Read one field and take a different branch for each value — urgent, normal, or anything else — instead of chaining yes/no questions.
-
schedule
set vars
Scheduled heartbeat
Runs on a timer and records a timestamped heartbeat. A good starting point for anything that should happen on a schedule.
-
webhook
Failure alert starter
An empty workflow with failure notifications already switched on, so you hear about it by email the moment a run breaks.
-
webhook
set vars
Clean up a webhook payload
Take a messy incoming webhook and turn it into tidy, predictable fields — lowercased emails, proper capitalisation, a formatted date — ready for whatever step you add next.
-
schedule
procore
email
Procore overdue RFI review
Pull the current Procore RFI register every morning and send the responsible team a review email. The guided step includes company, project, and automatic pagination controls.
Construction Use this -
schedule
procore
email
Procore daily log digest
Fetch a project's Procore daily construction reports on a schedule and deliver one operational digest, with typed date inputs and pagination already configured.
Construction Use this -
schedule
raken
email
Raken daily report digest
Collect completed and unsigned Raken daily reports for a project, follow every result page automatically, and email one concise review package to the site team.
Construction Use this -
schedule
raken
email
Raken time-card review
Retrieve Raken time cards for a project and date range with worker, approval, break, cost-code, and attachment data, then send payroll one scheduled review email.
Construction Use this -
webhook
http
New signup → Slack
Post a tidy message to a Slack channel whenever someone signs up. Connect Slack once and this works for any signup webhook.
Slack Use this -
webhook
http
YakDesk ticket → Slack
Receive YakDesk ticket webhooks (Ticket Settings → Outbound webhooks) and post each event to a Slack channel.
Slack Use this -
webhook
http
Form submission → YakDesk ticket
Receive a form webhook and create a YakDesk ticket via POST /api/v1/tickets (Bearer API key).
Integration Use this -
webhook
ai
http
Webhook → AI extract → ticket
Receive free-form text, pull out structured fields with AI, and open a ticket from the result.
AI Use this