Skip to content
Tallyfy

Make.com actions and triggers

What the Make.com connector covers

Section titled “What the Make.com connector covers”

The official Tallyfy connector on Make (formerly Integromat) is built and maintained by Make, and it is live and verified on Make’s marketplace today at make.com/en/integrations/tallyfy ↗. Make generated it from Tallyfy’s public API, so Make owns and maintains its module set.

Actions by category

Section titled “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

The proposed expansion above would total 85 modules (81 action modules plus 4 trigger modules), up from the connector’s original 7, backed by 9 helper lookups (RPCs) that populate dropdowns like templates and users. This is a wishlist maintained in Tallyfy’s connector repo, not the current live module set on Make.

Triggers (polling)

Section titled “Triggers (polling)”

Make went from a single trigger to four. Tallyfy has no webhook subscription API, so each trigger polls: it checks Tallyfy on the scenario’s 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 interval on the scenario schedule. More frequent polling means fresher data and more API calls.

Authentication

Section titled “Authentication”

Make.com connects to Tallyfy with a Tallyfy API token plus your Organization ID. Both are in your Tallyfy Settings. That keeps setup simple: paste the token once and the connection is ready.

Because the token acts on behalf of the user who created it, use a token from an account with the right permissions for what your scenarios do.

Getting started

Section titled “Getting started”
  1. Create a Make account and start a new scenario.
  2. Add the official Tallyfy connector and create a connection with your Tallyfy API token and Organization ID.
  3. Pick an action module, for example Start process, and map the input fields.
  4. To react to Tallyfy events, add one of the four trigger modules and set the scenario schedule.
  5. Test with sample data, then activate the scenario.

AI-native alternative (Tallyfy MCP)

Section titled “AI-native alternative (Tallyfy MCP)”

If building scenarios 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.

Section titled “Related articles”

Middleware > Make

Make (formerly Integromat) has an official, Make-maintained Tallyfy connector, live on Make’s…
Get in touch
About Tallyfy