Skip to content
Tallyfy

Celigo actions and triggers

What the Celigo connector now covers

The Celigo integration for Tallyfy was expanded from a few starter flows to a full set that mirrors what Tallyfy’s other connectors do. You can now build integrator.io flows for the same core actions across ten categories, plus four triggers.

Actions by category

CategoryWhat you can do
Users and guestsInvite members, read and list users, change roles, enable or disable accounts, create and update guests
GroupsCreate, read, update, and delete groups
TasksCreate standalone tasks, complete tasks (including approvals), update, reopen, and read tasks; list your tasks or a process’s tasks
ProcessesLaunch a process from a template, read, update, archive, reactivate, and list processes
TemplatesRead, list, create, clone, update, and delete templates; manage kick-off form fields
Form fieldsAdd, update, move, delete, and reorder step form fields and kick-off fields
Comments and issuesAdd comments, edit or delete them, report an issue on a task, and resolve an issue
TagsCreate, update, and delete tags; tag or untag templates and processes
FoldersCreate, update, and delete folders; move templates and processes in and out
SearchKeyword search across tasks, processes, templates, snippets, or everything at once

In total the connector now ships 86 flows, up from 4.

Triggers (scheduled delta-poll)

Celigo went from zero triggers to four. Tallyfy has no webhook subscription API, so each trigger is a scheduled delta-poll flow: it checks Tallyfy on a schedule, picks up new items, and de-duplicates by record id so nothing repeats.

  1. New process launched - a process starts, optionally scoped to one template.
  2. Task completed - a task is marked complete.
  3. Task assigned to you (new task) - a new task lands in your queue.
  4. Comment or issue added - a comment or reported issue appears on a watched task or process.

Set the poll frequency on the flow’s schedule. More frequent polling means fresher data and more API calls.

Authentication (OAuth 2.0 via integrator.io)

Celigo connects to Tallyfy with OAuth 2.0 through integrator.io. Contact Tallyfy support to get a Client ID and Client Secret, then create an HTTP connection in integrator.io using those credentials. OAuth is the right choice for production flows where more than one person authorizes access, and Tallyfy supports bearer tokens with refresh.

A personal access token also works for quick tests: go to Settings > Integrations > REST API in Tallyfy and copy your token. It acts on behalf of your own user account.

Getting started

  1. Create or open a flow in integrator.io.
  2. Add a Tallyfy HTTP connection and authenticate with your OAuth 2.0 credentials (or a personal token for testing).
  3. Pick an action, for example Launch process, and map the input fields.
  4. To react to Tallyfy events, add one of the four trigger flows and set its schedule.
  5. Test with sample data, then turn the flow on.

Remember the API terminology: “templates” in the Tallyfy UI are “checklists” in the API, and “processes” are “runs”.

AI-native alternative (Tallyfy MCP)

If building flows by hand is more than you need, the Tallyfy MCP server lets an AI assistant call these same actions in plain English. See the MCP server guide.

Middleware > Celigo

Celigo’s integrator.io platform can connect to Tallyfy through its universal HTTP connector and…
Get in touch
About Tallyfy