Workflow automation

Automate on the graph

Graph-native workflow automation on Gyri runs stored DAGs on your workspace graph — with triggers, agent steps, serverless invoke, container apps, graph tunnels, and cross-workspace federation — authored via natural-language buildout requests or MCP.

Triggers → agents → Lambda → federation. Say what you want — Gyri builds it.

Start free trial See how it works

Related: Zapier replacement guide · Agents write-back · CS AI workflows

Competitor matrix

Gyri vs automation tools

Start free trial
The problem

Why Zapier-style tools
stall.

How it scales

Small triggers.
Big graph.

Trigger
DAG
Agent
Compute
Graph
Natural language

Describe it. Gyri builds it.

No drag-and-drop required.

Buildout queues async. MCP edits are instant.

Use cases

Three starter
patterns.

Gyri think verbs

Agents that remember
what they conclude.

Gyri think verbs turn federated search into a research lifecycle — recall prior insights, ground in live CRM, reflect drafts, promote cited conclusions that compound across Claude, Cursor, and stored agents.

think verb=recall

Semantic orient — load prior cited conclusions before you re-derive from scratch.

think verb=ground

FTS-only orient on live federated CRM, email, and Slack — zero embed cost.

think verb=consider

Classify novelty against the workspace corpus before you commit a thesis.

think verb=reflect

Capture drafts, tensions, and questions as typed thoughts on the graph.

think verb=traverse

Multihop GraphQL in one think call — deal → contact → email → ticket.

think verb=fetch

Hydrate full rows by ref when search or traverse surfaced the right node.

Thought verbs deep dive · Claude + Gyri · Cursor + Gyri

One workflow. Full graph.

Free trial — describe your automation or migrate one context-heavy Zap.

Start free trial Get started guide

Frequently asked questions

How is Gyri different from Zapier or n8n?

Zapier and n8n move field values between apps on triggers. Gyri workflows query and mutate a federated workspace graph — CRM, email, Slack, docs — with cited synthesis, agent steps, and insight persistence before write-back.

What trigger types does Gyri support?

Four trigger kinds: custom_record (graph row change), poll (scheduled cadence), webhook (signed inbound POST), and insight (graph-native intel events).

Can I describe workflows in natural language?

Yes. Submit a buildout_request in plain language or use the wish think verb — Gyri queues workspace configuration including types, connectors, and workflows. Agents can also create workflows directly via MCP in session.

Does Gyri replace Zapier entirely?

Not always. Keep Zapier for simple field-mapping between two SaaS apps. Move context-heavy automations — enrichment, cited briefs, renewal radar — to Gyri where federated search and agent judgment matter.

What compute can workflows invoke?

Workflows can invoke AWS Lambda or GCP Cloud Functions via serverless_invoke, Gyri Cloud Run container apps via container_invoke, and local or tunnel-attached HTTP via graph tunnels — metered per plan.