Skip to content
Tallyfy

n8n actions and triggers

What the n8n node now covers

The Tallyfy community node for n8n (n8n-nodes-tallyfy) already had the broadest coverage of any Tallyfy connector, and it grew again. It went from 55 operations to 96, covering the same ten action categories as Tallyfy’s other connectors, and it gained something it never had before: a Tallyfy Trigger node with four triggers.

Actions by category

CategoryWhat you can do
Users and guestsInvite members, read and list users, change roles, enable or disable accounts, read your organization’s details, create, update, and delete guests, and convert members to guests (or back)
GroupsCreate, read, update, and delete groups
TasksCreate standalone tasks, complete tasks (including approvals), update, reopen, clone, and delete tasks; list your tasks, another member’s, a guest’s, or a process’s tasks
ProcessesLaunch a process from a template, read, update, archive, reactivate, and list processes; submit or reopen a kickoff form
TemplatesRead, list, create, clone, update, and delete templates; list a template’s steps and read its kickoff form fields
Form fieldsSet form field values on tasks; add, update, move, and delete step form fields; manage dropdown options; add, update, delete, and reorder kickoff fields
Comments and issuesAdd comments (including bot comments that skip notifications), edit or delete them, list a task’s comments, report an issue on a task, and resolve an issue
TagsList, create, update, and delete tags; tag or untag templates and processes
FoldersList, create, update, and delete folders; move templates and processes in and out
SearchKeyword search across tasks, processes, templates, snippets, or everything at once; six ID Finder lookups turn a name into the ID you need

In total the node now ships 96 operations across 12 resources, up from 55. In the node’s Resource dropdown you’ll see Blueprint, Process, Task, Form Field, Comment, User, Guest, Group, Tag, Folder, Search, and ID Finder.

Triggers (polling)

n8n went from zero triggers to four, in a dedicated Tallyfy Trigger node. Each trigger polls: it checks Tallyfy on the schedule you set, 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 process (a single process, or every process from one template).

Set the poll frequency on the trigger node’s schedule. More frequent polling means fresher data and more API calls. The first poll after you activate a workflow takes a snapshot, so the trigger only fires for items that show up after that. It won’t replay your history.

Authentication (personal access token)

n8n connects to Tallyfy with a Tallyfy API credential that holds two required values: your personal access token and your Organization ID. Get the token from Settings > Integrations > REST API in Tallyfy; your Organization ID is in your Tallyfy URL. A third field, the API base URL, comes pre-filled, so you can leave it alone.

The token acts on behalf of the user who created it. Use a token from an account with the right permissions for what your workflows do. The credential also has a built-in test that checks the token against your own Tallyfy profile, so you’ll know it works before you build anything.

Getting started

  1. Install the Tallyfy community node - on a self-hosted instance, run npm install n8n-nodes-tallyfy.
  2. In n8n, create a Tallyfy API credential with your access token and Organization ID, then run the credential test.
  3. Add a Tallyfy node to a workflow, pick a resource and operation, for example Process > Launch, and map the input fields.
  4. To react to Tallyfy events, add a Tallyfy Trigger node, choose one of the four triggers, and set its poll schedule.
  5. Test with sample data, then activate the workflow.

Remember the naming: “templates” in the Tallyfy UI show up as Blueprints in the node (the API also calls them “checklists”), and “processes” are “runs”. The full setup walkthrough, including the HTTP Request alternative, is in Connecting n8n.

AI-native alternative (Tallyfy MCP)

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

N8N > Connecting n8n

n8n connects to Tallyfy in about five minutes using either a community-built Tallyfy node or…
Get in touch
About Tallyfy