Start free
AActionAgile CRMUpdated June 2026

How do I update a contact in Agile CRM?

Short answer: You can update contact in Agile CRM by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Agile CRM Update Contact action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 7 Agile CRM 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
Contact ID
contact_id
stringRequiredContact ID. Example: 123456
First Name
first_name
stringOptionalContact's first (given) name.
Last Name
last_name
stringOptionalContact's last (family) name.
Email
email_value
stringOptionalEmail
Phone
phone
stringOptionalPhone number in E.164 format (with country code, no spaces).
Sample request
{
  "contact_id": "e.g. 123456",
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe",
  "email_value": "{{trigger.email_value}}",
  "phone": "e.g. +14155551234"
}
Returns
{
  "id": 123456,
  "properties": [
    {
      "name": "first_name",
      "value": "John"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for Update Contact.

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

A
Gmail → Agile CRM
1 Gmail triggers
A
Slack → Agile CRM
13 Slack triggers
A
Google Sheets → Agile CRM
2 Google Sheets triggers
A
HubSpot → Agile CRM
18 HubSpot triggers
FAQ

Questions about Update Contact.

What does the Update Contact action do in Agile CRM?
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.
What inputs does Update 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 Update Contact support batch operations?
Yes. Run Update Contact inside a Loop node to process arrays. TinyCommand 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.
Action
Create 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.
Action
Create 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.
Action
Create 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.
Action
Delete 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.
Action
Get Contact
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.