GravityDocs
Getting started
Building agents on Gravity
A reference for how agents are built and published on Gravity: the workflow engine, which pieces are supported, the AI capabilities, the Publish Gate, and the builder-question system.
Video walkthrough
Explore the docs
GuidelinesThe bar every submitted agent is reviewed against: ten rules that separate an agent from a tool.Workflow engineWhat Activepieces is, how it differs from n8n, and why Gravity runs on it.Supported piecesEvery piece in an uploaded workflow is checked at publish. Here is what passes, what is blocked, and why.AI capabilitiesAll AI in agents runs through one universal AI piece with six actions, powered by Gravity's managed provider.The Publish GateThe safety piece that keeps real actions from firing while an agent is being built or tested.Builder questionsThe questions an end user answers before running an agent, and how to define them well.BindAnswer once, fill the same property across several nodes.
Quick reference
| Topic | Key fact |
|---|---|
| Engine | Activepieces (self-hosted); agents are AP flows, consumers run private clones |
| Blocked pieces | Commercial AI providers: OpenAI, Azure OpenAI, Azure AI Foundry, Anthropic, Claude, AWS Bedrock, Google Gemini, Vertex AI, Mistral, Cohere, Perplexity, Groq, DeepSeek, Grok |
| Also unsupported | Chat trigger; file upload; Activepieces Tables and Database; audio files; Cloud-only pieces; unknown piece slugs (checked at publish) |
| AI | One universal AI piece, six actions (Ask AI, Summarize, Generate Image, Classify, Extract Structured Data, Run Agent) via managed OpenRouter; swapped to metered gravity-piece-ai at publish |
| Publish Gate | Optional right now (publishing works without it); when present, real actions below it never run in builds or previews |
| Builder questions | Ask-user switch per field at publish; plain-language question text written by the builder |
| Bind | One answer fans out to the same property across selected nodes |
Learn Activepieces
Gravity agents are Activepieces flows underneath, so the upstream material is the fastest way to get fluent with the builder:
For AI assistants
Building with ChatGPT, Claude, Cursor, or another AI assistant? These docs ship in a machine-readable form it can actually read. Paste one of these URLs into your assistant at the start of a session:
- — the complete docs as one markdown file. Use this one when the assistant is helping you build or fix an agent.
- — a short index with the key facts and rules, when you want to spend fewer tokens.
Both stay in sync with these pages, so an assistant working from them knows the current guidelines, the blocked pieces, and the things it should never wire into a flow (like the "Approval (Legacy)" piece).