n8n actions and triggers

What the n8n node now covers

Section titled “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 that runs in two modes, polling and instant webhooks.

Available now on npm

The expanded operation set (96 operations) and the new Tallyfy Trigger node are published on npm in version 1.1.1, so npm install n8n-nodes-tallyfy gives you the full set today. Version 1.1.1 also includes the fix for encoding choice-field values (dropdown, multiselect, and radio) when you pass them into a kickoff form on launch.

Actions by category

Section titled “Actions by category”

Category	What you can do
Users and guests	Invite 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)
Groups	Create, read, update, and delete groups
Tasks	Create 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
Processes	Launch a process from a template, read, update, archive, reactivate, and list processes; submit or reopen a kickoff form
Templates	Read, list, create, clone, update, and delete templates; list a template’s steps and read its kickoff form fields
Form fields	Set 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 issues	Add 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
Tags	List, create, update, and delete tags; tag or untag templates and processes
Folders	List, create, update, and delete folders; move templates and processes in and out
Search	Keyword 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.

Not yet included

Automation rules, step-level template edits (adding, cloning, reordering, or reassigning individual steps), and a raw API passthrough operation are a later follow-up. For those, use n8n’s built-in HTTP Request node with Tallyfy’s Open API.

Triggers (polling)

Section titled “Triggers (polling)”

The Tallyfy Trigger node runs in two modes, chosen with the Mode dropdown when you add it: Polling (works everywhere today) and Instant (Webhook) (real time, covered below). In Polling mode it checks Tallyfy on the schedule you set, picks up new items, and de-duplicates by record id so nothing repeats. The four polling triggers:

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.

Triggers (instant, webhook-based)

Section titled “Triggers (instant, webhook-based)”

Switch the node’s Mode to Instant (Webhook) and Tallyfy pushes events to n8n the moment they happen, so the workflow runs in real time instead of on the next poll. One node covers seven events, and you tick the ones you want in the Events list:

1. Process launched (process.launched) - a process is launched from a template.
2. Process completed (process.completed) - a whole process reaches completed status.
3. Task completed (task.completed) - a task is marked complete.
4. Task assigned (task.assigned) - a task is assigned to someone.
5. Comment added (task.comment_added) - a comment is posted on a task.
6. Issue raised (task.issue_raised) - an issue is reported on a task.
7. Issue resolved (task.issue_resolved) - a reported issue is resolved.

When you activate the workflow, the node registers one organization-wide webhook with Tallyfy and removes it when you deactivate. Tallyfy then posts every selected event to that single webhook.

Instant mode needs an org admin, and the backend is rolling out

Registering an organization webhook requires an organization admin token. A non-admin token gets a permission error on activation, so either connect an admin account or switch the node back to Polling mode. Tallyfy’s organization-webhook backend is also still rolling out to production, so until your organization has it enabled an instant trigger may not fire. Use Polling mode meanwhile, then switch to Instant once your organization has it.

Authentication (personal access token)

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

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

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

Related articles

Section titled “Related articles”

N8N > Connecting n8n

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

Middleware > n8n

n8n is a developer-friendly automation platform with a dedicated Tallyfy connector. It offers 96…

Workato > Workato actions and triggers

The Workato connector for Tallyfy grew from five actions and three triggers to a full set…

Middleware > Connector capability matrix

Every Tallyfy middleware connector (Zapier, Power Automate, Workato, Celigo, Make.com, and n8n)…

Was this helpful?

YesNo