The jsonStringify helper converts a value into JSON text. Use it when a template needs the JSON for an object or array you already have in context, such as a child object taken from a parsed payloa...
Your Celigo account is the central hub for managing your profile, subscriptions, environments, security, and team invitations.This guide serves as the starting point for account administration. It ...
The storage activity log records what happened to the files and folders in Celigo Storage — who did it, when, and from where. It covers every source that can reach storage, so you can answer "who d...
A Celigo File storage connection lets your flows read, write, and manage files in Celigo Storage the same way they use any other file provider, such as Amazon S3, FTP, or Google Drive. There are no...
Configure Amazon Redshift as your Celigo sync destination and let the sync manage the warehouse side for you: it creates the destination schema and tables on the first run and keeps them in step wi...
Deleting a tool moves it to the recycle bin, where it stays for 30 days — or until your data retention policy removes it — before it's gone for good. You can't delete a tool while any flow, API, AI...
A tool's input and output are each defined by a JSON schema, and every run is validated against both: the caller's record against the input schema before the tool runs, and the result against the o...
Downloading a tool packages it, with every nested tool, lookup, import, and script it uses, as a zip file you can keep, share, or upload into another account or environment — for example, to promot...
Moving a tool changes which integration it belongs to without copying it — the same tool, with the same references from flows and agents, appears under a different integration. Use it to gather sha...
Cloning creates an independent copy of a tool — with every nested tool, lookup, import, script, lookup cache, and custom API it uses — in the integration and environment you choose. Use it to make ...