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.

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

Yes. Because you run Jentic One yourself, your own rules decide which Flowup operations and credentials the agent may use. You can allow only the calls it needs, such as listing flows with GET /flows or triggering a run with POST /executions, while excluding flow creation via POST /flows unless you explicitly permit it. The stored API key is injected into the Authorization header only for the operations you have allowed, so the agent cannot reach beyond that scope.