Flowup API

Name: Flowup API API
Brand: Flowup API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey3 EndpointsREST

For Agents

List, create, and trigger workflow executions in Flowup so an agent can drive process automation from external events.

Connect the Flowup API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flowup 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 Flowup API API.

List defined workflow flows in the Flowup account via GET /flows

Create a new workflow flow with definition payload via POST /flows

Trigger a flow execution with input parameters via POST /executions

Drive event-triggered automation by mapping external events to Flowup executions

GET STARTED

Start building with Flowup API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for Flowup API, keeping it validated and agent-ready. Flowup provides a workflow automation surface for defining flows and triggering executions against them. The API is a thin three-endpoint surface: list flows, create a flow, and trigger an execution. Authentication is via an Authorization header API key, suitable for programmatic flow runs from external triggers such as document events or schedule-based jobs.

Use Cases

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

★ Event-Triggered Workflow Execution

Trigger Flowup workflows in response to events emitted by other systems — for example, a new document landing in a folder or a lead reaching a specific stage. The agent calls POST /executions with the target flow id and input payload, letting Flowup orchestrate the downstream steps. This avoids embedding orchestration logic in every source system.

POST /executions with flow id 'invoice_approval' and the new invoice payload to start the approval workflow.

Programmatic Flow Authoring

Define new workflow flows from code so process changes are versioned alongside the rest of the codebase. The agent calls POST /flows with a definition payload, then validates it landed by listing flows via GET /flows. This pattern suits teams that treat workflow definitions as configuration-as-code rather than UI-only artefacts.

POST /flows with a new flow definition for 'document_intake', then GET /flows to confirm the flow appears in the catalog.

Flow Catalog Discovery

Inspect the catalog of available flows before deciding which automation to invoke — useful when an agent receives a freeform request and needs to map it to a concrete Flowup flow id. The agent calls GET /flows to enumerate the available definitions and selects the closest match. This avoids hard-coding flow ids inside callers.

GET /flows and return the list of flow names and ids to the caller for selection.

AI Agent Workflow Orchestration

Through Jentic, an AI agent can take 'run the invoice approval workflow with these line items' and resolve it to Flowup's POST /executions operation without browsing docs. Jentic injects the API key from the vault and validates the execution payload schema. End-to-end setup is under an hour from sign-up.

Use Jentic search for 'trigger a Flowup workflow', load the POST /executions operation, and execute it with flow id 'invoice_approval' and the input payload.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/flows

List flows

POST

/flows

Create a flow

POST

/executions

Trigger a flow execution

GET

/flows

List flows

POST

/flows

Create a flow

POST

/executions

Trigger a flow execution

Why though Jentic?

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

Credential isolation

Flowup API keys are stored encrypted in the Jentic vault and injected as the Authorization header at execution time. Agents receive a scoped reference, never the raw key.

Intent-based discovery

Agents search by intent (e.g. 'trigger a Flowup workflow') and Jentic returns the POST /executions operation with its input schema, so the agent calls the right endpoint without reading docs.

Time to first call

Direct Flowup integration: a few hours for auth wiring and execution payload mapping. Through Jentic: under 30 minutes from sign-up to first execution triggered.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Monday.com API

Monday.com offers automation recipes inside its work-management surface; Flowup is a leaner workflow trigger API.

Choose Monday.com when the workflow is owned inside the work-management UI. Choose Flowup when a thin headless workflow trigger is enough.

Alternative

Asana API

Asana drives task-based workflows with rule automations; Flowup is a generic flow execution trigger.

Choose Asana when the work units are tasks owned by a team. Choose Flowup when the workflow does not need a task UI.

Complementary

Google Drive API

Drive can host the documents that trigger a Flowup execution.

Use Drive when the trigger is a new document or a folder change. Use Flowup to run the resulting automation.

FAQs

Specific to using Flowup API API through Jentic.

Why is there no official OpenAPI spec for Flowup API?

Flowup does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Flowup 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 Flowup API use?

Flowup uses an API key passed in the Authorization request header. Through Jentic, that key is stored encrypted in the vault and injected at execution time, so it never enters the agent's context.

Can I trigger a workflow execution programmatically?

Yes. POST /executions accepts a flow id and input payload, and starts the corresponding flow run. Use GET /flows first to discover the catalog of available flow ids.

How do I trigger a Flowup workflow through Jentic?

Run pip install jentic, search for 'trigger a Flowup workflow', load the POST /executions operation, and execute it with the flow id and input payload. Jentic returns the input schema so the agent assembles a valid request without reading docs.

Can I create new flows from the API?

Yes. POST /flows accepts a flow definition payload and creates a new workflow. This lets teams treat flow definitions as configuration-as-code rather than UI-only artefacts.

What are the rate limits for the Flowup API?

The published spec does not declare explicit per-endpoint limits. Build retry-with-backoff into your client and treat 429 responses as the signal to slow down. For high-volume execution triggers, confirm thresholds with Flowup directly.