Celigo provides powerful error-handling features to help you manage and remediate issues efficiently in your Tools. With automated error logging and detailed error messages, you can quickly diagno...
Performing a high-volume real-time webhook flow in debug mode may cause increased connection queue size (253k to 152k) causing the flow to run slowly. This can lead to flow failure and can also aff...
The Logs tab in tool builder shows the invocation history for tools called by AI agents, MCP servers, or third-party applications. Logs appear only when the invoking resource's log mode isn't set t...
Guardrails help you protect your flow by checking each record for safety and compliance as it runs. It works in real time and can be placed before or after an AI agent, or anywhere in the flow. Cr...
What's new Celigo AI delivers descriptive resource summaries, intuitive code assistance, and intelligent auto-mapping Resource descriptions With the help of Celigo AI, you can instant...
Tools participate in ILM the same way flows and integrations do. Use ILM to move tool changes safely between environments, such as sandbox, staging, and production. Tool definitions, dependencies,...
To see the guardrails in your account, navigate to AI studio → Guardrails. Note If you haven’t added any guardrails yet, click Create guardrail to add one. The guardrails list view displays key ...
Input control defines how you pass data from a flow to a guardrail. Correct input setup ensures consistent evaluation per record: Pass the correct context for evaluation Combine structured re...
APIs and tools both execute logic in integrator.io, but they serve different purposes. Use this guide to decide which to build. It is recommended to build reusable logic as a tool and if external ...
A guardrail returns structured JSON output for every record. This output is consistent across all policy types and cannot be modified. At minimum it includes the decision: flagged (true/false). De...