OtherReal-timeUpdated May 2026

Directus

Directus open-source data backend

Directus is the open-source headless CMS + data platform — wraps your SQL database with an admin UI and auto-generated REST/GraphQL APIs, used by developers who want CMS-like UI but on their own database schema. Tiny Command exposes one action, no triggers (Directus has webhook configuration in admin Settings → Webhooks; point at a Tiny Command webhook trigger URL): Get Item (fetch a record from a Directus collection by ID). The connection takes the Directus instance URL plus an access token. For workflows that need to read or update data in a Directus-managed database (CMS content, application data, internal tools), this is the bridge. Directus's value vs Strapi or Contentful is that it works on top of your existing database — no separate data store. For new projects, evaluate Directus alongside Contentful (better hosted) and Strapi (similar shape, different ecosystem).

Connect Directus

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Directus can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Directus Item	Returns a record from a Directus collection by ID. For "fetch this CMS-managed content" or "look up this user-managed config row" workflows that integrate Directus-managed databases with downstream tools.	2 fields	View →

Recipes

Pre-built Directus workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Directus → Slack alerts

AI-triage every Directus event, ping the right channel only when it matters.

Directus → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Directus → Notion database

Turn Directus into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Directus once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Directus field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Directus integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Directus to Tiny Command?

Open the Tiny Command workflow builder, drop in a Directus node, and click Connect. Authorize Directus once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Directus triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Directus today. Use Tiny Command's universal Webhook or Schedule trigger to start Directus workflows, then run any Directus action you need.

What Directus actions can I run from a workflow?

1 Directus action are available out of the box, covering other operations like "Get Directus Item". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Directus integration real-time?

Directus actions execute synchronously inside your workflow. Tiny Command waits for Directus's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Directus with Tiny Command?

No. Every Directus trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Directus API endpoint directly.

How much does the Directus integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Directus integration itself has no per-app surcharge.