Dazyflow is in early access. Request an invite
Dazyflow
Request an invite

Step catalog ​

🧭 New to Dazyflow? Start with Concepts and the Glossary — they explain flows, steps, wiring, triggers, and the words used below.

Every step you can add to a flow. Apps & services connect an outside account; Triggers decide when a flow starts; Building blocks are the standard toolkit for moving and shaping data.

Apps & services ​

Connect the account once on the Apps page, then use these steps in any flow.

46elks ​

ChatGPT ​

Claude ​

Collections ​

  • Collections — Find rows — Read rows from one collection with no-code filters (column / operator / value), an optional sort and limit; emits rows plus column names.
  • Collections — Query with SQL — Run a SELECT against the workspace's Collections and emit rows plus column names; an empty collection returns an empty result.
  • Collections — Save rows — Append rows to a workspace-local collection with zero setup; auto-creates the collection, evolves columns on the fly, and surfaces the rows under Collections.

Discord ​

Email ​

  • Email — Send email — Send an email through any mail server (SMTP) — daily summaries, alerts, or a build's output straight into someone's inbox.

Excel ​

Fortnox ​

  • Fortnox — Create customer — Create a customer in Fortnox — the entry point of most billing automations (form signup → customer → invoice).
  • Fortnox — Create invoice — Create an invoice in Fortnox for a customer — the headline billing step (customer → invoice).
  • Fortnox — List invoices — Read invoices from Fortnox, filtered by status — the building block for a 'fire on newly paid invoice' flow.

Git ​

  • Git — Checkout — Clone a remote git repository into the workspace and optionally check out a specific branch, tag, or commit SHA.
  • Git — Diff — Produce a unified diff (patch text) between two git refs in a checked-out workspace repo.
  • Git — Log — Walk a checked-out repo's history and return recent commits with SHA, author, timestamp, and summary.

GitHub ​

  • GitHub — Add comment — Add a comment to a GitHub issue or pull request.
  • GitHub — Create issue — Open a new issue on a GitHub repo with title, body, labels and assignees.
  • GitHub — List issues — List issues on a GitHub repo filtered by state, labels, assignee, and update time. Pull requests are excluded by default.
  • GitHub — On new PR — Trigger that fires once when a pull request is opened on a connected GitHub repo.
  • GitHub — On push — Trigger that fires when commits are pushed to a connected GitHub repo, with ref, SHAs, and commit list.

Gmail ​

  • Gmail — Read email — Read one email — who sent it, the subject, the date, and the body.
  • Gmail — Search emails — Find emails in the connected mailbox, using the same search you'd type in Gmail.
  • Gmail — Send email — Send an email as the connected Gmail account, with optional CC/BCC, HTML, and file attachments.

Google Calendar ​

Google Drive ​

Google Forms ​

Google Sheets ​

HTTP ​

Home Assistant ​

Klarna ​

  • Klarna — Capture order — Capture a Klarna order when the goods ship — fully, or a partial amount.
  • Klarna — Get order — Look up a Klarna order by id — status and the captured / refunded / remaining amounts.
  • Klarna — Refund order — Refund a captured Klarna order, fully or partially — pairs with an approval step upstream.

MQTT ​

MySQL ​

  • MySQL — Insert rows — Batch-insert rows into a MySQL/MariaDB table inside one transaction; auto-creates the table from headers when missing.
  • MySQL — Query — Run a parameterized SELECT against MySQL/MariaDB and emit rows plus column names as a result set.
  • MySQL — Upsert rows — Insert-or-update rows in MySQL/MariaDB via INSERT ... ON DUPLICATE KEY UPDATE, matching existing rows on the conflict columns.

Notion ​

  • Notion — Create page — Add a page to Notion — a row in a database or a subpage — with a title and body text.
  • Notion — Query database — Read rows from a Notion database — each row comes out as simple column → value pairs.

Open-Meteo ​

OpenStreetMap ​

OpenWeather ​

Postgres ​

  • Postgres — Insert rows — Batch-insert rows into a Postgres table inside one transaction; auto-creates the table from headers when missing.
  • Postgres — Query — Run a parameterized SELECT against Postgres and stream rows back as a result set with typed values.
  • Postgres — Upsert rows — Insert-or-update rows in Postgres via INSERT ... ON CONFLICT, matching existing rows on the conflict columns.

Roaring ​

SMHI ​

SQLite ​

  • SQLite — Insert rows — Save rows into a workspace database file — no setup; the table is auto-created from the row shape.
  • SQLite — Query — Run a parameterized SELECT against a workspace-sandboxed SQLite file and emit rows plus column names.
  • SQLite — Upsert rows — Insert-or-update rows in a workspace-sandboxed SQLite file via INSERT ... ON CONFLICT, matching on the conflict columns.

Slack ​

Stripe ​

  • Stripe — Cancel subscription — Cancel a Stripe subscription — at period end by default, so the customer keeps what they paid for.
  • Stripe — Create customer — Create a Stripe customer — the entry point of most billing automations (form signup → customer).
  • Stripe — Create payment link — Mint a shareable Stripe payment link for a price — wire the URL straight into an email or Slack message.
  • Stripe — Create refund — Refund a Stripe payment, fully or partially — pairs naturally with an approval step upstream.
  • Stripe — List events — Read recent Stripe events — the building block for 'fire on new payment / failed invoice / new subscription' flows.
  • Stripe — List subscriptions — List a customer's Stripe subscriptions (or sweep all of them by status) — the lookup step before a cancel.
  • Stripe — On payment — Trigger that fires the moment a Stripe payment succeeds, with amount, currency and payer email.
  • Stripe — On payment failed — Trigger that fires when a Stripe payment attempt fails, with the decline reason ready for an alert.
  • Stripe — On subscription canceled — Trigger that fires when a Stripe subscription ends — churn alerts, offboarding, win-back flows.
  • Stripe — Search customers — Find Stripe customers with the dashboard's search syntax — the lookup step before a refund or update.
  • Stripe — Send invoice — Bill a Stripe customer a one-off amount and email them the invoice — draft, line item, finalize and send in one step.

Twilio ​

Webhook ​

nShift ​

ntfy ​

Triggers ​

Every flow starts with one of these — on a schedule, or when something arrives.

Triggers ​

  • Interval — Starts the flow over and over at a fixed pace — e.g. every 5 minutes.
  • Schedule — Starts the flow on a schedule — daily, weekly, monthly or hourly.
  • Webhook — Starts the flow when its form is submitted or its web address receives data.

Building blocks ​

The standard toolkit: decisions, loops, and tools to shape text, data, files and dates.

Files ​

Flow control ​

  • Branch — Forward the input down the Yes or No port based on a Yes/No value input.
  • Compare — Compare A against B with a chosen operator and emit true or false on the Yes/No output.
  • Contains — Forward the Text down Yes or No based on whether it contains the Substring.
  • Delay — Hold the flow for a fixed number of milliseconds before forwarding the input downstream.
  • For each — Fan out a list and run the wired loop body on every item, optionally in parallel, collecting results in order.
  • If — Test A with a chosen operator and forward it down the Yes or No port.
  • Merge — Synchronize parallel branches by collecting every upstream input into a single list emitted on out.
  • Reusable flow — Invoke another graph as a reusable step, seeding its inputs and projecting selected child outputs back up.
  • Switch — Route the input payload to one of N case ports by matching a key against each case value; unmatched goes to default.
  • Wait for approval — Pause until a person approves: hand a link to your notify step, then continue on their decision.

Logic & comparisons ​

  • A < B — Emit true when A is less than B, else false.
  • A = B — Emit true when A equals B, else false.
  • A > B — Emit true when A is greater than B, else false.
  • A AND B — Emit true on the Yes/No output only when every wired input is true.
  • A OR B — Emit true on the Yes/No output when any wired input is true.
  • A ≠ B — Emit true when A does not equal B, else false.
  • A ≤ B — Emit true when A is less than or equal to B, else false.
  • A ≥ B — Emit true when A is greater than or equal to B, else false.
  • NOT — Negate the boolean input: emit true when the input is false, and false when it is true.

Network & HTTP ​

System ​

Transform data ​