FlowSOP Connect

The execution layer that plugs into the tools you already use

ClickUp, Monday.com, Maestro, your CMMS, or your internal ERP already create your work orders. FlowSOP doesn't replace them — it connects them to the field: a simple link, no install, with photo proof and live status flowing back automatically.

View documentation

How it fits together

Your current tools

ClickUp
Jira
Monday.com
Maestro
CMMS / EAM
FlowSOP API
FlowSOP
Simple link
Field
Webhooks

Status, photos and completion flow back live to your source tool

Create the work order where you already work

FlowSOP receives the event, generates the execution link, and sends progress back.

ClickUp

Automation or outbound webhook to the FlowSOP API

Jira

Native Jira Automation (no app) to the FlowSOP API

Monday.com

Native integration or via Zapier/Make

Maestro

Construction ERP — connect via API or scheduled export

CMMS / EAM

Maintenance work order → field execution with proof

Internal ERP

Direct connection via API key and signed webhooks

Any other system

Any platform capable of an HTTP call can connect

No native connector for your tool yet? You don't need to wait for one.

FlowSOP exposes a simple REST API and signed webhooks — exactly what Zapier and Make expect. One generic connector already covers 7,000+ apps, with no per-platform development.

Zapier

Trigger a FlowSOP work order from any trigger, and send status back to your tool.

Make (Integromat)

Visual multi-step scenarios — great for syncing FlowSOP with several systems at once.

Direct API

For an internal technical team: API key + HMAC webhooks, no middleman.

In 3 steps

1. Create

Your system sends a POST to the FlowSOP API with the title, tasks and recipient.

2. Execute

FlowSOP generates an execution link — the field crew opens it on their phone, no account or install needed.

3. Receive

Every step (started, task completed, work order finished) triggers a signed webhook back to your tool.

Technical overview

Full documentation is available from your dashboard (Settings → Integrations) once you've created an API key.

Create a work order

POST /api/v1/work-orders
Authorization: Bearer fsk_live_...
Content-Type: application/json

{
  "title": "Inspection compresseur A-12",
  "tasks": ["Vérifier pression", "Photo du manomètre"],
  "assignee_email": "tech@example.com",
  "external_source": "clickup",
  "external_id": "task-8842"
}

Check status

GET /api/v1/work-orders/:id
Authorization: Bearer fsk_live_...

Update or cancel

PATCH /api/v1/work-orders/:id     { "due_date": "2026-09-01" }
DELETE /api/v1/work-orders/:id    (annulation — récupérable 90 jours)

Verify a webhook signature

X-FlowSOP-Signature: sha256=<hmac>
X-FlowSOP-Timestamp: <unix_ms>

signature = HMAC-SHA256(secret, timestamp + "." + body)

Webhook event catalog

Every event sends a signed POST with this envelope: { event, timestamp, data }.

mission.created

A new work order was created (via the API or the dashboard).

"data": { "mission_id": "a1b2c3d4-...", "title": "Inspection compresseur A-12",
  "external_source": "clickup", "external_id": "task-8842" }
mission.started

The executor opened the link and started the work order in the field.

"data": { "mission_id": "a1b2c3d4-..." }
task.completed

A single task was just completed.

"data": { "mission_id": "a1b2c3d4-...", "task_id": "f7e8...",
  "task_title": "Vérifier pression" }
mission.completed

Every task is done — the work order is closed.

"data": { "mission_id": "a1b2c3d4-...", "tasks_count": 4 }

CMMS or ERP team? Let's talk technical.

If you're evaluating an integration with your existing CMMS or ERP, our team can discuss architecture, security and volume directly with you.

See our Security & Compliance page
Talk to an expert

Ready to connect your first tool?

30-day free trial, no credit card required.