--- title: Workato · Tallyfy Pro description: Tallyfy's Workato connector, built on Workato's Ruby SDK with OAuth 2.0, starts processes, completes tasks, and tracks assignments across enterprise systems. It is in development and not yet in Workato's library, so contact Tallyfy support for early access. lastUpdated: 2026-07-27T00:00:00.000Z source_url: html: https://tallyfy.com/products/pro/integrations/middleware/workato/ md: https://tallyfy.com/products/pro/integrations/middleware/workato/index.md --- ## Workato connector for Tallyfy Tallyfy has built a Workato connector on Workato’s Ruby SDK. It connects Tallyfy to enterprise systems through Workato’s recipe-based automation, so once it’s available you’ll be able to launch processes, complete tasks, and track assignments across your tech stack without switching tools. Not yet available to install This dedicated connector is built but not yet published to Workato’s community library, so you can’t add it from inside Workato today. [Contact Tallyfy support](https://tallyfy.com/products/pro/miscellaneous/support/how-can-i-contact-tallyfys-support-team/) for early access. You can still connect Workato to Tallyfy right now using Workato’s HTTP connector with [Tallyfy’s REST API](https://tallyfy.com/products/pro/integrations/open-api/). The how-to guides below use exactly that approach. ### What the connector does The connector now covers a full set - 82 actions and 10 triggers (5 polling and 5 instant webhook) - detailed in [Workato actions and triggers](https://tallyfy.com/products/pro/integrations/middleware/workato/workato-actions-and-triggers/). The core actions and triggers below cover the most common integration patterns. **Actions:** * **Start process** - launches a new process from a template, with dynamic kick-off form fields pulled from the template’s configuration * **Complete task** - marks a task as done, optionally submitting form data along with it * **Update task** - changes a task’s name, description, deadline, or assignees (users, guests, or groups) * **Add comment** - posts a comment or problem report on a specific task * **Get process** - retrieves process details, optionally including all its tasks **Triggers (polling-based):** * **New task assigned** - fires when a task gets assigned to the connected user * **Process completed** - fires when a process reaches completed status * **New process started** - fires when a new process is created, with optional filtering by template ### How authentication works The connector uses OAuth 2.0. You’ll need three pieces of information to set up the connection: 1. **Client ID** - from your Tallyfy OAuth application 2. **Client Secret** - from the same OAuth application 3. **Organization ID** - found in Tallyfy Settings > Organization The OAuth flow goes through `account.tallyfy.com/oauth/authorize` for authorization and `account.tallyfy.com/oauth/token` for token exchange. Workato handles token refresh automatically, so you won’t deal with expired sessions. Every API call includes the `Authorization` bearer token header and an `X-Organization-ID` header. ### Architecture overview ```plaintext Your Systems → Workato Platform → Tallyfy API ↓ ↓ ↓ Salesforce Recipe Engine Start Process SAP Data Transform Complete Task Workday Error Handling Update Task ServiceNow Polling Triggers Add Comment ``` ### Dynamic kick-off form fields When you pick a template in the “Start process” action, the connector fetches that template’s kick-off form fields and generates matching input fields in Workato. It maps Tallyfy field types to Workato controls - text, number, date, dropdown, multiselect, boolean, email, and URL fields all get proper input types. This means your recipes can pass data directly into Tallyfy’s kick-off forms without manual field mapping. ### Example scenarios **Deal-to-onboarding:** When a deal closes in Salesforce, a Workato recipe starts a Tallyfy customer onboarding process. The recipe maps the customer name, contract value, and account manager from CRM fields into the kick-off form. **Task completion sync:** The “process completed” trigger watches for finished Tallyfy processes, then pushes status updates to your ERP or project management tool. **Assignment routing:** The “new task assigned” trigger picks up fresh assignments and sends notifications through Slack, Teams, or email - whatever your team prefers. ### Key API endpoints used The connector talks to Tallyfy’s REST API at `https://go.tallyfy.com/api`. Every call is scoped to your organization, so `{org}` below is your Organization ID: * `POST /organizations/{org}/runs` - start a new process from a template (the template is the `checklist_id` in the request body) * `POST /organizations/{org}/completed-tasks` - complete a task * `PUT /organizations/{org}/runs/{run}/tasks/{task}` - update a task * `POST /organizations/{org}/tasks/{task}/comment` - add a comment to a task * `GET /organizations/{org}/runs/{run}` - get process details * `GET /organizations/{org}/tasks` - list tasks (used by the assignment trigger) * `GET /organizations/{org}/runs` - list processes (used by the process triggers) * `GET /organizations/{org}/checklists` - list templates for dropdown pick lists ### API terminology mapping * “Templates” in the UI = “Blueprints” or “Checklists” in the API * “Processes” in the UI = “Runs” in the API * “Form fields” in the UI = “Captures” in the API * “Steps” in templates = “Tasks” in running processes ### Guest assignment rules The connector enforces Tallyfy’s business rule that guests (external users) can’t be the sole assignees on a task. If you assign only guest email addresses, the connector automatically adds the current user as a co-assignee. It also validates guest emails against the organization domain - if someone with an internal email is listed as a guest, the connector looks up their user ID instead. ### Error handling The connector returns clear error messages for common failures: * **401** - authentication failed, token refresh needed * **403** - missing organization access * **404** - resource doesn’t exist or user lacks access * **422** - validation errors with field-level details * **429** - rate limit exceeded ### Getting early access The dedicated connector isn’t in Workato’s library yet, so you can’t self-install it. To join the early-access group: 1. Contact [Tallyfy support](https://tallyfy.com/products/pro/miscellaneous/support/how-can-i-contact-tallyfys-support-team/) to request the connector and OAuth credentials. 2. Once support provides them, set up the connection in Workato with your Client ID, Client Secret, and Organization ID. 3. Build recipes using the connector’s actions and triggers. 4. Test with a sandbox template before going live. Prefer not to wait? Use Workato’s HTTP connector with [Tallyfy’s REST API](https://tallyfy.com/products/pro/integrations/open-api/) today, following the how-to guides below. * [**Complete Tallyfy tasks from Workato**](https://tallyfy.com/products/pro/integrations/middleware/workato/how-to-complete-tallyfy-tasks-from-workato/) * [**Launch Tallyfy processes from Workato**](https://tallyfy.com/products/pro/integrations/middleware/workato/how-to-launch-tallyfy-processes-from-workato/) * [**Workato actions and triggers**](https://tallyfy.com/products/pro/integrations/middleware/workato/workato-actions-and-triggers/) ## Related articles [**Workato > Workato actions and triggers**](https://tallyfy.com/products/pro/integrations/middleware/workato/workato-actions-and-triggers/) The Workato connector for Tallyfy grew from five actions and three triggers to a full set… [**Workato > Launch Tallyfy processes from Workato**](https://tallyfy.com/products/pro/integrations/middleware/workato/how-to-launch-tallyfy-processes-from-workato/) Workato recipes can automatically launch Tallyfy processes from triggers in Salesforce, Zendesk… [**Middleware > Connector capability matrix**](https://tallyfy.com/products/pro/integrations/middleware/connector-capability-matrix/) Every Tallyfy middleware connector (Zapier, Power Automate, Workato, Celigo, Make.com, and n8n)… [**Celigo > Celigo actions and triggers**](https://tallyfy.com/products/pro/integrations/middleware/celigo/celigo-actions-and-triggers/) The Celigo connector for Tallyfy grew from a handful of flows to a full set covering users… ## Was this helpful?