Actions7
Execute Crew
AI-generatedSummary
Execute a specified Ordify crew by its crew ID, optionally providing a message and structured input data, with the choice to either receive the job ID immediately (async) or wait for the job's completion, polling at configurable intervals and timing out after a set period.
Inputs
- Crew ID (required) — The identifier for the crew to execute.
- Message — Optional text message to send to the crew, used especially when invoking schema-driven jobs with input data.
- Input Data JSON — Optional structured JSON object to be passed as input data to the crew. Must be a valid JSON object if provided.
- Execution Mode (required) — Controls whether to execute asynchronously (return job ID immediately) or wait for the job to complete (poll status).
- Poll Interval Seconds — When waiting for completion, the number of seconds between each status poll (1 to 60 seconds).
- Timeout Seconds — Maximum number of seconds to wait for the job to reach a terminal status before timing out (5 to 3600 seconds).
Output shape
a single item per execution with JSON containing at minimum the job ID and execution details
If Execution Mode is 'async', returns an object with job ID and initial response. If 'wait', polls job status until terminal state or timeout, then includes final status, job status response, and job result if successful. Throws error if input data JSON is invalid or if timeout occurs.
Examples
Example 1: Execute a crew asynchronously providing a message and input data
Crew ID set to 'crew123', message 'Start process', input data with parameters, execution mode set to async. Returns immediately with job ID.
Example 2: Execute a crew and wait for completion
Crew ID set to 'crew123', no message, input data empty, execution mode set to wait, poll interval 5 seconds, timeout 300 seconds. Returns after job finishes, including job result data.