What a task is
In Tray.ai’s model, a “task” is one execution of a workflow for one trigger event. If a workflow runs when a Salesforce opportunity is created, each new opportunity produces one task. If a workflow runs on a schedule, each scheduled run is a task.
Tasks are observable — each has a trace with step-level timing, inputs/outputs at every step, and success or failure outcome.
Why it matters in pricing
Usage-based pricing in the integration category often meters “something.” For Tray.ai, that metric is tasks: the number of times workflows run. Pricing discussions typically involve estimating the volume of tasks your use cases will generate, and scoping accordingly.
See the pricing page for current commercial structure.
Scale context
Tasks at Tray.ai scale:
- Cisco runs 600M+ tasks per year across 60+ automations.
- DocuSign runs 150M tasks per month.
- Auctane processes 3B orders per year through Tray.ai.
Those numbers give a sense of what “tasks” actually means in production — not a rate limit to worry about, but a normal unit of work at enterprise scale.
Where you see tasks
The Intelligent iPaaS pillar surfaces task counts, per-workflow volume, per-step execution details — the observability layer of the platform. Anywhere you’re running process automation or data integration, tasks are the thing being counted.