- Integrations
- /
- AgencyHandy
- /
- Actions
- /
- Assign Task to Team Member
ActionAgencyHandyUpdated May 2026
How do I assign an AgencyHandy task to a specific team member?
Short answer: Drop the "AgencyHandy → Assign Task to Team Member" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Task ID taskId | string | Required | Task ID |
Member ID memberId | string | Required | Member ID |
Sample request
{"taskId": "{{trigger.taskId}}","memberId": "{{trigger.memberId}}"}
Returns
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Assign Task to Team Member.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Assign Task to Team Member.
What does the Assign Task to Team Member action do in AgencyHandy?
Sets or changes the assignee on a specific task. The team member gets a notification per their AgencyHandy preferences. Useful for round-robin distribution workflows or "auto-assign to whoever owns this client account" routing logic.
What inputs does Assign Task to Team Member require?
Required: Task ID, Member ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if AgencyHandy returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Assign Task to Team Member support batch operations?
Yes. Run Assign Task to Team Member inside a Loop node to process arrays. Tiny Command handles AgencyHandy's rate limits automatically so you don't have to throttle manually.
More actions
Other AgencyHandy actions.
Action
Complete Task
Transitions a task to the completed state, which fires the Task Completed trigger downstream. Useful for cascading workflows that auto-close tasks based on external signal (e.g., CI build green → mark deployment task done).
ActionCreate Client Group
Groups bundle multiple client contacts under one company-level entity for shared billing, portal access, and project organisation. Use when onboarding a new client company whose contacts will all share access to the same projects and invoices.
ActionCreate Invoice
Creates a draft invoice for a client with line items, taxes, and due date. Optionally auto-send the invoice email via the send_email flag. The standard hook for "project complete → auto-bill the agreed amount" workflows; for recurring retainers, schedule this on a monthly cron instead.
ActionCreate Lead
Captures a prospect at the top of the funnel — before they've become a paying client. Useful as the receiver for marketing-website form submissions; AgencyHandy's pipeline then tracks them through proposal → client conversion.
ActionCreate Order
Provisions a new order with services, line items, client reference, and pricing. Skips the client-facing storefront step — useful when a sales call closes by phone or email and you want to log the order rather than send a proposal.
ActionCreate Subtask
Nests a subtask under a parent task. Useful for breaking down complex tasks into smaller checklist items, with each subtask separately assignable and trackable. Parent task can't complete until all subtasks finish (configurable per-account).
Send assign task to team member from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.