Middleware > Integrate Tallyfy with Workato
Complete Tallyfy tasks from Workato
This guide explains how to complete Tallyfy tasks programmatically from Workato recipes. This enables you to update task progress based on events in other systems, creating seamless cross-platform workflows.
- Mark tasks complete when a document is signed in DocuSign
- Complete approval tasks based on responses in Microsoft Forms
- Update task form fields when data changes in your CRM
- Auto-complete tasks when specific conditions are met in your ERP
- Workato account with HTTP connector access
- Tallyfy API token from Settings > Integrations > REST API
- Task IDs or a method to retrieve them dynamically
- Understanding of your task’s form fields
You need the task ID to complete it. There are several ways to obtain this:
If Tallyfy triggered your Workato recipe via webhook:
task_id = trigger["task"]["id"]
Use an HTTP GET request to find tasks:
GET https://go.tallyfy.com/api/tasks?run_id={process_id}
When launching processes, store the returned task IDs in a lookup table or database for later use.
- Add an HTTP action to your Workato recipe
- Configure the request:
- Method: PUT
- URL:
https://go.tallyfy.com/api/tasks/{task_id}/complete
- Headers:
Content-Type: application/json
X-Tallyfy-Client: APIClient
- Add the request body with form field data
If the task has form fields that need values, include them in the request body:
{ "form_fields": { "approval_status": "Approved", "approver_name": "John Smith", "approval_date": "2024-03-15", "comments": "Looks good, approved for implementation" }}
Map fields from your trigger data:
{ "form_fields": { "invoice_number": trigger["invoice"]["number"], "amount": trigger["invoice"]["total"], "payment_status": trigger["payment"]["status"], "processed_by": trigger["user"]["email"] }}
Only complete tasks when specific conditions are met:
- Add a conditional action before the HTTP request
- Check your conditions:
trigger["order"]["status"] == "shipped" ANDtrigger["order"]["payment_status"] == "paid"
- Place the completion HTTP action inside the conditional block
To complete multiple tasks in a process:
- First, get all tasks for a process:
GET https://go.tallyfy.com/api/tasks?run_id={process_id}&status=active
- Use a For each loop in Workato
- Inside the loop, complete each task that matches your criteria
- Add a 1-second delay between completions to avoid rate limits
To update task form fields without marking the task complete:
PUT https://go.tallyfy.com/api/tasks/{task_id}
Request body:
{ "captures": { "field_name": "updated_value", "status": "In Progress" }}
Error Code | Meaning | Solution |
---|---|---|
401 | Unauthorized | Check API token and headers |
404 | Task not found | Verify task ID and that it exists |
400 | Invalid data | Check form field names and data types |
422 | Validation failed | Ensure required fields are provided |
- Click the error handler icon on your HTTP action
- Add a Retry action for transient failures
- Configure retry settings:
- Max attempts: 3
- Interval: 5 seconds
- Backoff multiplier: 2
- Add logging for permanent failures
Here’s a complete recipe pattern:
- Trigger: DocuSign - Document completed
- Action 1: Search Tallyfy tasks by document ID
GET https://go.tallyfy.com/api/tasks?search={document_id}
- Action 2: Parse response to get task ID
- Action 3: Complete the task with signature details
{"form_fields": {"signed_by": "{{trigger.signer_email}}","signed_date": "{{trigger.completed_date}}","document_url": "{{trigger.document_url}}","signature_id": "{{trigger.envelope_id}}"}}
- Action 4: Send confirmation email
- Cache frequently used task IDs
- Use batch operations when possible
- Implement connection pooling for high-volume scenarios
- Monitor API usage against rate limits
- Validate data before sending to Tallyfy
- Log all completions for audit trails
- Implement rollback mechanisms for critical workflows
- Use idempotency keys to prevent duplicate completions
- Never expose API tokens in logs
- Use Workato’s secure storage for credentials
- Implement field-level encryption for sensitive data
- Audit recipe access regularly
- Verify the task is in “active” status
- Check all required form fields are provided
- Ensure the assigned user has permission
- Confirm the task hasn’t already been completed
- Field names must match exactly (case-sensitive)
- Check data types (string vs number vs boolean)
- Verify field exists in the task template
- Ensure values meet field validation rules
- Add delays between requests
- Implement exponential backoff
- Batch operations where possible
- Contact Tallyfy support for higher limits if needed
- Set up webhooks to trigger completions in real-time
- Create reusable functions for common operations
- Build error notification workflows
- Implement comprehensive logging and monitoring
Workato > Launch Tallyfy processes from Workato
Zapier > Automate tasks in Tallyfy using zaps
- 2025 Tallyfy, Inc.
- Privacy Policy
- Terms of Use
- Report Issue
- Trademarks