EBCloud
Connect EBCloud to ActionFlows
EBCloud provides AI models you can use in ActionFlows. The API address is maas-api.ebcloud.com.
About EBCloud
EBCloud is an AI provider you can use in ActionFlows. EBCloud provides AI models you can use in ActionFlows. The API address is maas-api.ebcloud.com.
Use EBCloud in ActionFlows
Connect EBCloud in your ActionFlows organization. Agents and playground nodes can then run its models. After you save the credentials, EBCloud is available in ActionFlow.
Frequently asked questions
AI providers (OpenAI, Anthropic, and others in the catalog) and apps your team already uses. The integrations directory is the live list. MCP servers cover extra tools that speak the protocol.
Usually no. You add organization credentials, then pick the integration or MCP server on a node or in Studio. Custom HTTP tools exist when a catalog item is not enough.
The public catalog groups integrations and models by job: language, images, speech, data, agent tools, and more. Open Integrations to see current categories. We do not freeze that list in this FAQ.
You can attach multiple providers and apps on one organization. Plan limits still apply to runs, storage, and related quotas. See the pricing table.
Integration credentials stay on the organization, not on a single ActionFlow. Access follows organization membership. Use minimum access on the provider side as well.
Yes. Nodes and agent tools expose the fields that matter for that operation. HTTP tools and MCP cover cases that are not in the catalog.
API keys are usually minutes. OAuth apps follow that provider's consent screen. After that, reuse the same connection on any ActionFlow or agent in the organization.
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.