Skip to content
Tallyfy

Workato actions and triggers

What the Workato connector now covers

Section titled “What the Workato connector now covers”

The Workato connector for Tallyfy is built to cover the same core actions as Tallyfy’s other connectors, across ten categories plus ten triggers (five polling and five instant webhooks). Once it’s published, you’ll be able to build recipes for all of them.

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 tasks for yourself, another member, a guest, or a process
ProcessesLaunch a process from a template, read, update, archive, reactivate, and list processes; submit or reopen a kick-off form
TemplatesRead, list, create, clone, update, and delete templates; list a template’s steps and kick-off fields
Form fieldsAdd, update, move, and delete step form fields; manage dropdown options; add, update, delete, and reorder kick-off fields
Comments and issuesAdd, read, edit, and delete comments; report an issue on a task and resolve it
TagsCreate, update, delete, and list 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 82 actions and 10 triggers (5 polling and 5 instant), up from 5 actions and 3 triggers, backed by 5 pick lists that fill dropdowns like templates, users, and processes.

Triggers (polling)

Section titled “Triggers (polling)”

Workato went from three triggers to five - it already had more working triggers than any other Tallyfy connector. Each trigger polls: it checks Tallyfy on a schedule, picks up new items, and de-duplicates by record id so nothing repeats.

  1. New process started - a process starts, optionally scoped to one template.
  2. Task completed - a task is marked complete.
  3. New task assigned - a new task lands in your queue.
  4. Comment or issue added - a comment or reported issue appears on any task in the process you choose to watch.
  5. Process completed - a whole process reaches completed status, not just one task.

Polling frequency follows your Workato plan and recipe settings. More frequent polling means fresher data and more API calls.

Triggers (instant, webhook-based)

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

Five more triggers deliver in real time instead of polling. Tallyfy pushes the event to your recipe the moment it happens. Each has an (instant) title in the trigger picker:

  1. New process launched (instant) - fires the moment a process is launched from a template.
  2. Process completed (instant) - fires the moment a whole process reaches completed status.
  3. Task completed (instant) - fires the moment a task is marked complete.
  4. New task assigned (instant) - fires the moment a task is assigned to someone.
  5. New comment or issue (instant) - fires when a comment is added, or an issue is raised or resolved, on a task.

When the recipe starts, the connector registers one organization-wide webhook with Tallyfy and removes it when the recipe stops. Tallyfy then posts every event to that webhook, and each instant trigger keeps only the events it cares about.

Authentication (OAuth 2.0)

Section titled “Authentication (OAuth 2.0)”

Workato connects to Tallyfy with OAuth 2.0. Contact Tallyfy support to get a Client ID and Client Secret, then create a Tallyfy connection in Workato using those credentials plus your Organization ID (find it in Settings > Organization). Tallyfy supports bearer tokens with refresh, so the connection renews itself and you won’t keep re-entering credentials.

Getting started

Section titled “Getting started”
  1. Create or open a recipe in Workato.
  2. Add the Tallyfy connector and create a connection with your OAuth 2.0 Client ID, Client Secret, and Organization ID.
  3. Pick an action, for example Start process, and map the input fields.
  4. To react to Tallyfy events, start the recipe from one of the five polling triggers.
  5. Test with sample data, then start the recipe.

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

AI-native alternative (Tallyfy MCP)

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

If building recipes 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 > Workato

Tallyfy’s Workato connector, built on Workato’s Ruby SDK with OAuth 2.0, starts processes…
Get in touch
About Tallyfy