AActionAgile CRMUpdated May 2026
How do I fetch a single Agile CRM contact?
Short answer: Drop the "Agile CRM → Get Contact" 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 |
|---|---|---|---|
Contact ID contact_id | string | Required | Contact ID. Example: 123456 |
Sample request
{"contact_id": "e.g. 123456"}
Returns
{"id": 123456,"properties": [{"name": "first_name","value": "John"},{"name": "email","value": "john@example.com"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Contact.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Contact.
What does the Get Contact action do in Agile CRM?
Returns the contact by ID or email with all standard and custom fields plus current tag set. The base lookup before update workflows or for enrichment patterns that need a CRM snapshot.
What inputs does Get Contact require?
Required: Contact 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 Agile CRM 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 Contact support batch operations?
Yes. Run Get Contact inside a Loop node to process arrays. Tiny Command handles Agile CRM's rate limits automatically so you don't have to throttle manually.
More actions
Other Agile CRM actions.
Action
Add Tag to Contact
Applies one or more tags to a contact — auto-creates tags that don't exist. Tags drive segmentation in Agile CRM's campaigns and reports, so consistent tag taxonomy matters; maintain a canonical list.
ActionCreate Contact
Inserts a new contact with standard fields (name, email, phone), optional custom fields, and initial tags. Agile CRM dedupes on email — duplicate emails get rejected with an error rather than upserting. Wrap in a Search-first pattern if you're unsure whether the contact exists.
ActionCreate Deal
Creates a new sales deal/opportunity tied to a contact. Set the value, expected close date, owner, and the milestone (Agile's pipeline stage). Useful for "form submission → log to CRM as opportunity" workflows.
ActionCreate Note on Contact
Attaches a free-text note to a contact, visible in the contact's activity timeline. Useful for "call summary from Aircall → append to CRM contact" workflows or for logging AI-generated summaries of customer interactions.
ActionDelete Contact
Hard-deletes the contact and all associated history. Irreversible. Used for GDPR right-to-erasure requests; for soft removal that preserves history, use a tag like "deleted" or move to a suppression list.
ActionUpdate Contact
Partial update on contact fields. Only passed fields change. For "enrich from external source → write back to CRM" workflows where you're augmenting existing records with firmographic or behavioural data.
Send get contact from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.
