Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflowfast.io%2Fflowfast" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fflowfast.io%2Fflowfast" | 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.

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

Forward FlowFast execution results back into a downstream system

GET STARTED

Start building with FlowFast API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use FlowFast 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 Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the FlowFast API by hand means setting its Authorization header key on every request and building your own retry and error handling around the flow-execution endpoints. Through Jentic you install once, import FlowFast from the API Directory, store the key once, and your agent calls it.

Permission scoping

FlowFast identifies the flow in the request body rather than the URL path, so scoping is operations-only: you limit the agent to the operations it needs, such as listing flows or reading executions, and leave out triggering a new execution unless you add it. Every operation the agent can run is one you chose.

Credential isolation

Your FlowFast API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

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

FAQs

Specific to using FlowFast 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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the FlowFast API?

Yes. Because Jentic One runs self-hosted, your own rules decide which FlowFast operations and credentials the agent may use. Since FlowFast names the flow in the request body rather than the URL, scoping is operations-only: you can allow the agent to list flows with GET /flows and read results with GET /executions while withholding POST /executions so it cannot trigger a new run unless you grant it. Every operation the agent can call is one you chose.

FlowFast API

Name: FlowFast API
Brand: FlowFast API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticDeveloper ToolsCi CdapiKey3 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to trigger a FlowFast automation by ID, I want to list all flows in my FlowFast workspace, Get the result of a specific FlowFast execution, Find a flow named 'send-welcome-email'

Not supported: Does not handle source control, deployments, or monitoring - use for triggering FlowFast flow executions and reading their results only.

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.

Jentic One on Github View OpenAPI Document

Connect the FlowFast API to your agent

Capabilities

Start building with FlowFast API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

FlowFast API