Install Jentic One Beta

Connect the Loopfour Workflows API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Loopfour Workflows 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%2Floopfour.com%2Floopfour" | 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%2Floopfour.com%2Floopfour" | 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 Loopfour Workflows API.

Discover workflow blocks and integration actions with listBlocks (kind core, integrations, or triggers) and getBlock for a type such as quickbooks

Trigger a workflow run in async or sync mode with an idempotencyKey to prevent duplicate runs

Read a run's status and logs, then cancel it, retry a failed run, or restart it from a specific fromStepId

Schedule a workflow with a cron or interval in a given timezone, or fire a scheduled run on demand

GET STARTED

Start building with Loopfour Workflows API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Loopfour Workflows API for, with concrete tasks.

★ Agent-operated finance workflows through Jentic

An operations agent asks Jentic for the Loopfour run operations, triggers a workflow with triggerWorkflowRun and an idempotencyKey, then follows it with getRun and getRunLogs. When a step fails it calls restartRun with the fromStepId of that step instead of rerunning the whole workflow. The x-api-key value stays in your self-hosted Jentic One instance.

Search Jentic for 'run a Loopfour workflow', call triggerWorkflowRun for workflow id 'wf_123' with mode 'async' and idempotencyKey 'close-2026-11', then poll getRun until it finishes

Failed run triage

A support routine calls listRuns with status and a from and to date window to find failures, reads getRunLogs for each, and either retries the run with retryRun or restarts it from the failing step with restartRun and optional overrideInput. Failed outbound notifications can be re-sent with retryWebhookDelivery.

Call listRuns with status 'failed', then call getRunLogs for each run id and summarize the failing step

Building workflows from integration actions

Start with listBlocks using kind integrations to see available providers, then getBlock for a type such as quickbooks to read its action ids and input definitions. createWorkflow takes a name, a trigger, and steps built from those actions, and activateWorkflow turns it on once a provider connection exists.

Call getBlock with type 'quickbooks', pick the action for creating an invoice, then call createWorkflow with name 'Invoice sync', a trigger, and one step using that action

Scheduled runs and versioned changes

Set a workflow's cron, interval, timezone, and enabled flag with updateWorkflowSchedule. Before shipping an edit, compareWorkflowVersions shows the difference between two versions, and rollbackWorkflowVersion restores the last good one if a change breaks a run.

Call updateWorkflowSchedule for workflow 'wf_123' with cron '0 7 * * 1-5', timezone 'Europe/Dublin', and enabled true

Key Endpoints

74 endpoints — the loopfour workflows api builds, triggers, and inspects deterministic finance workflows, the same ones you design on the loopfour canvas.

METHOD

PATH

DESCRIPTION

GET

/blocks

Discover workflow blocks and actions

POST

/workflows

Create a workflow

POST

/workflows/{id}/run

Trigger a workflow run

GET

/runs/{id}

Get a run

GET

/runs/{id}/logs

Get run logs

POST

/runs/{id}/restart

Restart a run from a step

PUT

/workflows/{id}/schedule

Update a workflow schedule

POST

/tables/{id}/rows/query

Query table rows

GET

/blocks

Discover workflow blocks and actions

POST

/workflows

Create a workflow

POST

/workflows/{id}/run

Trigger a workflow run

GET

/runs/{id}

Get a run

GET

/runs/{id}/logs

Get run logs

POST

/runs/{id}/restart

Restart a run from a step

PUT

/workflows/{id}/schedule

Update a workflow schedule

POST

/tables/{id}/rows/query

Query table rows

Why Jentic?

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

Setup

Wiring Loopfour by hand means sending its x-api-key header, unwrapping the success and data envelope, and polling async runs or tuning sync timeouts yourself. Through Jentic you install once, import Loopfour from the API Directory, store the key once, and your agent calls it.

Permission scoping

Loopfour puts the workflow id in the URL path for runs, schedules, versions, and secrets, so a rule can pin your agent to one workflow: it can trigger and inspect that workflow under /workflows/{id}/ and nothing else. You choose the operations it may call, so destructive ones like deleteWorkflow or deleteConnection are not included unless you add them.

Credential isolation

Your Loopfour 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 'run a finance workflow' or 'get run logs', and Jentic returns the matching Loopfour operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Loopfour Workflows API through Jentic.

What authentication does the Loopfour Workflows API use?

Per its OpenAPI spec, the Loopfour Workflows API uses an apiKey scheme: a key issued from your Loopfour workspace settings, sent in the `x-api-key` header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I run a Loopfour workflow synchronously?

Yes. POST /workflows/{id}/run accepts mode 'sync' with maxExecutionTimeMs between 1000 and 300000, plus onTimeout (return_run_id or throw_error) and onFailure (throw_error or switch_to_async). The default is async, and an idempotencyKey prevents duplicate runs.

What are the rate limits for the Loopfour Workflows API?

The OpenAPI spec does not specify rate limits. Check the Loopfour documentation for current limits, and use idempotencyKey on run triggers so retries do not start duplicate runs.

How do I restart a failed run with the Loopfour Workflows API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add the Loopfour Workflows API from the Jentic API Directory, and have your agent search for 'restart a workflow run'. Jentic returns restartRun (POST /runs/{id}/restart) with its schema, and the agent sends the required fromStepId plus optional overrideInput. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Loopfour MCP server?

You don't need an MCP server to give your agent the Loopfour Workflows API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, with operations discovered on demand instead of loading extra tool definitions into its context.

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

Yes. Write a rule that allows triggerWorkflowRun and listWorkflowRuns only on /workflows/wf_123/, plus getRun and getRunLogs. The agent can run and monitor that one workflow, while deleteWorkflow, the connection calls, and workflow secret operations are outside the allowed set, and every call it makes is logged.

Which integrations can Loopfour workflows use?

Call GET /blocks with kind integrations to list available integration blocks, or GET /blocks/{type} with a known type such as quickbooks to read its action ids, input definitions, requirements, and choices. Provider credentials are linked with the connection endpoints, either through an OAuth auth URL or an API key connection.

Loopfour Workflows API

AI ReadinessAI-Aware (B)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsData PipelinesapiKey (x-api-key header)74 EndpointsREST

For Agents

Create, schedule, and run Loopfour finance workflows, inspect run logs and retry or restart failed runs, manage provider connections, data tables, and workflow secrets, and send run events to webhook endpoints.

Use for: Run the month-end reconciliation workflow now, Check why last night's invoice sync run failed, Restart the failed run from the QuickBooks step, I want to schedule the AP workflow every weekday at 7am

Not supported: Does not keep a general ledger, file taxes, or move money between bank accounts itself. Use for building, scheduling, running, and monitoring Loopfour finance workflows only.

The Loopfour Workflows API builds, triggers, and inspects deterministic finance workflows, the same ones you design on the Loopfour canvas. You discover available blocks and integration actions such as QuickBooks, create a workflow from a trigger and steps, activate, pause, schedule, or run it synchronously or asynchronously with an idempotencyKey, and then read its runs and logs, cancel, retry, or restart a run from a chosen step. Supporting resources cover versioning with compare and rollback, LLM-backed extraction and classification agents that workflows call, OAuth and API key connections to third-party providers, data tables with row queries, workflow secrets, and outbound webhook endpoints with delivery retries.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

52%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

44%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

90%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Loopfour Workflows API to your agent

Capabilities

Start building with Loopfour Workflows API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Loopfour Workflows API

Jentic AI Readiness Score

Loopfour Workflows API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness