FlowFast API

Name: FlowFast API API
Brand: FlowFast API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi CdapiKey3 EndpointsREST

For Agents

Trigger FlowFast process automations, list available flows, and read back execution status from agent code.

Connect the FlowFast API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FlowFast API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with FlowFast API API.

List all flows defined in a FlowFast workspace

Trigger a specific flow execution with input parameters

Retrieve the status and output of a completed execution

Wire FlowFast flows into chat agents as a single tool call

GET STARTED

Start building with FlowFast API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for FlowFast API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for FlowFast API, keeping it validated and agent-ready. FlowFast is a process automation platform that lets teams define multi-step flows and run them on demand. The API exposes a small surface for listing flows, triggering executions, and retrieving execution results, with authentication via an Authorization header API key.

Use Cases

Patterns agents use FlowFast API API for, with concrete tasks.

★ Trigger Automations from Agents

Expose FlowFast flows as agent tools by listing them via /flows and triggering them through /executions. This lets an LLM-driven agent run prebuilt automations — for example, an onboarding flow — without the agent having to assemble the underlying steps. Setup is minutes once the API key is wired.

Trigger flow 'send-welcome-email' via POST /executions with input {email: 'user@example.com'} and return the resulting execution ID.

Flow Discovery for Agents

Pull the catalogue of available flows via GET /flows so an agent can decide which automation matches the user's request. The endpoint returns flow names and IDs that can be passed to /executions. Use this when the set of flows changes over time and you don't want to hardcode IDs.

Call GET /flows and return the names and IDs of all flows whose name contains 'invoice'.

Execution Result Polling

After triggering a flow, poll GET /executions to read the status and output. Useful when the agent needs the flow's output to continue the conversation, for example confirming a sent email or returning a generated document URL. Each execution has an ID and a terminal state once complete.

Poll GET /executions for execution ID 'exec_42' until status is 'success' or 'failed' and return the output payload.

AI Agent Integration via Jentic

Agents use Jentic's intent search to locate FlowFast operations, load the schema for /executions, and call it with a scoped credential. This is the recommended path for embedding FlowFast in MCP-based assistants where the agent needs to invoke business automations on behalf of a user. Jentic keeps the API key isolated.

Use Jentic to search 'trigger a FlowFast flow', load the POST /executions schema, and execute the flow chosen by the user with the input values they provided.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for flowfast api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/flows

List all flows in the workspace

POST

/executions

Trigger a flow execution

GET

/executions

List or read execution status and output

GET

/flows

List all flows in the workspace

POST

/executions

Trigger a flow execution

GET

/executions

List or read execution status and output

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The FlowFast Authorization header API key is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution token and never see the raw key, which keeps it out of prompts and logs.

Intent-based discovery

Agents search by intent (e.g. 'trigger a FlowFast flow') and Jentic returns the POST /executions operation with its input schema, so the agent triggers the right flow without browsing FlowFast docs.

Time to first call

Direct FlowFast integration: half a day for auth wiring, flow discovery, and result polling. Through Jentic: minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

n8n API

Open-source workflow automation platform with a much larger surface and self-hosted option.

Choose n8n when the user needs self-hosted automations, hundreds of node integrations, or a visual editor.

Alternative

Zapier NLA API

Hosted automation platform with thousands of app integrations.

Choose Zapier when the user wants to chain SaaS apps together with no infrastructure and pay-per-task pricing.

Complementary

Pipedream API

Code-first event workflows that pair with FlowFast for richer scripting needs.

Use alongside FlowFast when the team wants Node/Python steps in front of or behind a FlowFast flow.

FAQs

Specific to using FlowFast API API through Jentic.

Why is there no official OpenAPI spec for FlowFast API?

FlowFast does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call FlowFast API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the FlowFast API use?

The FlowFast API uses an API key passed in the Authorization header. Jentic stores the key encrypted in the MAXsystem vault and injects it on outbound calls so the agent never holds the raw secret.

Can I trigger flows on demand with the FlowFast API?

Yes, POST /executions starts a flow with the input you supply. The response includes an execution ID that you then read back via GET /executions for status and output.

What are the rate limits for the FlowFast API?

The OpenAPI spec does not declare explicit rate limits. Apply client-side throttling for bursty agent traffic and back off on 429 responses returned by the service.

How do I find the right flow to trigger through Jentic?

Search Jentic for 'list FlowFast flows', load the GET /flows schema, and execute the call. The returned list contains the IDs you pass to POST /executions when triggering the flow.