The Cloud AI category pieces (text-ai, image-ai, utility-ai, agent). Activepieces Cloud splits its AI actions across these four slugs; our instance bundles the same actions in a single piece. Templates using them are accepted and rewritten automatically, including known action renames (for example summarize becomes summarizeText).
GravityDocs
Platform
Supported and blocked pieces
Every piece in an uploaded workflow is checked at publish. Here is what passes, what is blocked, and why.
Two different rules apply here. First, a piece must exist in Gravity's Activepieces instance: at publish time every piece in the uploaded workflow is checked, and any piece that cannot be resolved is rejected with the message "Workflow uses pieces we don't support yet". Second, some pieces exist but are deliberately blocked by policy.
Blocked by policy: commercial AI provider pieces
Agents must run their AI through Gravity's managed AI, so pieces that would run on the builder's own API key or cloud account are blocked. They are hidden from the app-connection catalog and rejected when a workflow containing them is published. The blocked list:
| Provider family | Blocked pieces |
|---|---|
| OpenAI and Microsoft | OpenAI, Azure OpenAI, Azure AI Foundry |
| Anthropic | Anthropic, Claude |
| Amazon | AWS Bedrock |
| Google Gemini, Google Vertex AI | |
| Other commercial LLM APIs | Mistral AI, Cohere, Perplexity, Groq, DeepSeek, Grok (xAI) |
Two deliberate exceptions: open-source and open-weight model hosts (for example Hugging Face and Stability AI) are allowed, and Gravity's own managed AI path (the universal AI piece, gravity-piece-ai, and the OpenRouter gateway it routes through) is never blocked because it is the intended way to use AI in agents.
Not supported for other reasons
| What | Detail |
|---|---|
| Chat trigger | The chat interface trigger (piece-forms, chat_submission). Published agents must start from a supported trigger; use the Web Form trigger instead when the agent needs user input at run time. |
| File upload | Users cannot upload files to an agent. Collect the content through the matching app instead: a Google Sheet for CSV data, a Google Doc or Word file for documents — the same pattern for any file type. |
| Activepieces Tables | The built-in Tables product is not available. Use Google Sheets instead — it does the same job, and the agent can create the sheet itself on its first run. |
| Activepieces Database | Not available on our instance. Use a real database piece instead, such as MongoDB or Oracle. |
| Audio files | Agents cannot receive or process audio. There is no workaround yet. |
| Activepieces Cloud exclusive pieces | Pieces that exist only on Activepieces Cloud and are not published to the public registry (for example Cloud-only premium integrations). They fail the availability check at publish. |
| Unknown or unpublished custom pieces | Any piece slug our instance cannot fetch from the npm registry. |
Often confused with unsupported — but supported
Supported triggers
Supported triggers, for completeness: Web Form, Webhook, Schedule, Manual, and app piece triggers (both polling and webhook styles).