Agent Workflow

Push Agent Workflow

Changed on

Push Bluejay's stored workflow back to the agent's source provider.

force=true bypasses DFCX conflict detection (use when you want to overwrite remote drift). Non-DFCX providers ignore the flag.

create_version=true (DFCX only) snapshots the flows/playbooks the push actually changed into new immutable versions, recording them in the version ledger. Snapshotting only-changed resources keeps version counts down and is why it rides on push: the remote draft only reflects Bluejay's edits after a successful push.

Returns 409 with {conflicts} when remote has drifted and force is False. Returns 207 with {results} when some DFCX SDK calls succeed and some fail.

post/v1/agents/{agent_id}/workflow/push

Request

  • Base URL
    https://api.getbluejay.ai
  • URL
    https://api.getbluejay.ai/v1/agents/{agent_id}/workflow/push
  • Auth
    HTTPBearer (a scheme the document does not define)

Path parameters

agent_idstring required

Query parameters

branch_idstring nullable
forceboolean
create_versionboolean
version_descriptionstring nullable

Headers

X-Organization-Idstring
X-API-Keystring required

API key required to authenticate requests.

Response

Successful Response

unknown required

Changes