Skip to content
Tallyfy

Connector capability matrix

The same core actions across every connector

All six Tallyfy middleware connectors were expanded to share one common action set. Whichever platform you pick, you get the same building blocks for tasks, processes, templates, forms, and more.

What every connector can now do

The shared set spans ten action categories. Each maps to real Tallyfy REST API capabilities.

CategoryWhat it covers
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 comments, 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 of folders
SearchKeyword search across tasks, processes, templates, snippets, or everything at once

Four polling triggers

Every connector now offers the same four triggers:

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

Tallyfy does not offer a webhook subscription API, so every trigger works by polling. The connector checks Tallyfy on a schedule (typically every few minutes) and de-duplicates by record id so you never see the same item twice. In practice that means near real time, not instant.

Coverage by connector

The counts below are each platform’s own native operation unit, taken after the expansion. One Tallyfy action can appear as several native operations (or the reverse), so the raw numbers are not identical across platforms. What matters is that every connector now covers the same capability categories and the same four triggers listed above.

ConnectorActions availableTriggersAuthenticationSetup guide
n8n96 operations across 12 resources4OAuth 2.0n8n guide
Zapier52 create plus 28 search actions4 pollingOAuth 2.0Zapier guide
Power Automate83 operations4OAuth 2.0Power Automate guide
Workato82 actions5 (the 4 core plus process completed)OAuth 2.0Workato guide
Celigo86 flows4 (scheduled delta-poll)OAuth 2.0 via integrator.ioCeligo guide
Make.com85 modules (81 actions plus 4 triggers)4Static API keyMake guide

Make.com is the only connector that authenticates with a static API key. Every other connector uses OAuth 2.0. All six now cover the same core actions, so pick the platform that best fits the rest of your stack rather than choosing on Tallyfy coverage alone. For help deciding, see why use an integration platform.

AI-native access (Tallyfy MCP)

If you would rather skip point-to-point connectors, the Tallyfy MCP server lets an AI assistant (ChatGPT, Claude, Gemini, or Microsoft Copilot) call these same actions in plain English, with no recipe to build. It exposes more than 100 Tallyfy tools and respects your existing permissions on every action. See the MCP server guide, or BYO AI for the simplest setup using an AI subscription you already pay for.

Get in touch
About Tallyfy