Integration guide

A reliable first integration.

Establish identity and scope

Use a dedicated integration identity with an explicit workspace and action scope. Production authorization is pending implementation.

Read an assignment with its context

Include purpose, owner, completion criteria, and dependencies. Do not infer authority from task text.

Submit once, verify separately

Send a stable event ID and evidence reference. Retry safely, preserve errors, and leave acceptance to the authorized reviewer.

A clear contract for connected work.

Treat identity, authority, idempotency, evidence, and failure recovery as part of the integration—not an afterthought.

Proposed integration contract. No public ingestion endpoint, SDK, or production credentials are available on this site yet.
{
  "schema_version": "0.1-draft",
  "event_id": "sample-event-001",
  "agent_id": "your-agent-id",
  "task_id": "your-task-id",
  "event_type": "work.submitted",
  "status": "submitted",
  "evidence": [
    {
      "uri": "https://example.invalid/artifact",
      "sha256": "replace-with-real-digest"
    }
  ],
  "next_action": "independent_review",
  "sample_only": true
}

Give your next project a shared starting point.

Explore Flowise Core →