Celigo
70/ 100
CScore Breakdown70%
Lost points on 5 checks
- time0/15
- efficiency0/10
- zero errors0/5
- Context70/14
- OpenAPI0/14
Eval Score (70% weight)70%
cost$0.04 (<$0.05, excellent)+10
time313s (≥300s, too slow)+0
efficiency44 tool calls (>25, inefficient)+0
found docsTouched docs at developer.celigo.com: yes (7 matching tool calls)+10
zero errorsTool outputs with errors/tracebacks: 1+0
syntax validCode compiles/parses correctly+5
created filesGenerated files: 2 (need ≥1)+10
full executionMethod: full_execution, Exit: 0+35
Final Score
A: >=90%B: 75-89%C: 55-74%D: <55%
(70 × 0.7) + (71 × 0.3)= 70%
Replay
Using https://developer.celigo.com, complete the following task: Using Celigo, build me a script that creates, validates, or inspects a workflow automation: 1. Install and use the official Celigo SDK if one is available; otherwise use the documented REST API 2. List existing workflows, scenarios, zaps, connectors, or equivalent automation resources 3. Create or configure a workflow if the API supports creation; otherwise retrieve a workflow definition and explain which trigger/action primitives are available 4. The workflow should model this process: - Trigger: inbound webhook with a lead record - Step 1: normalize fields name, email, company, employee_count, and message - Step 2: branch high_priority=true when employee_count >= 500 or the message contains "enterprise" - Step 3: route high-priority leads to sales and all others to nurture 5. If the API supports *****ing/running the workflow, run it with one sample enterprise lead and one sample self-serve lead 6. Print JSON with fields: platform, workflow_id, trigger_type, steps, *****_runs, and notes Use real documented Celigo APIs or SDK calls. Do not simulate the full workflow only in local Python unless Celigo exposes no create/***** API and you clearly report the limitation after inspecting documented resources.
opencode.json
Unlock analytics
See Celigo's score trend, layer rankings, and competitive position.
Run completed Oct 23, 2026, 6:56 AM