Start free
ActionAgencyHandyUpdated June 2026

How do I look up an AgencyHandy team member?

Short answer: You can get team member in AgencyHandy by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AgencyHandy Get Team Member action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 27 AgencyHandy actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Member ID
memberId
stringRequiredMember ID
Sample request
{
  "memberId": "{{trigger.memberId}}"
}
Returns
{
  "_id": "abc123",
  "email": "john@example.com",
  "lastName": "Doe",
  "firstName": "John"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Team Member.

Any of these apps can fire this action as part of a workflow.

Gmail → AgencyHandy
1 Gmail triggers
Slack → AgencyHandy
13 Slack triggers
Google Sheets → AgencyHandy
2 Google Sheets triggers
HubSpot → AgencyHandy
18 HubSpot triggers
FAQ

Questions about Get Team Member.

What does the Get Team Member action do in AgencyHandy?
Returns a team member's profile by ID — name, email, role, active projects, current task load. Useful for resolving assignee IDs to readable names in downstream notifications and for capacity-aware assignment workflows.
What inputs does Get Team Member require?
Required: 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 Get Team Member support batch operations?
Yes. Run Get Team Member inside a Loop node to process arrays. TinyCommand handles AgencyHandy's rate limits automatically so you don't have to throttle manually.
More actions

Other AgencyHandy actions.

Action
Assign Task to Team Member
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.
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).
Action
Create 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.
Action
Create 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.
Action
Create 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.
Action
Create 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.