Add Tag to Contact: Agile CRM action

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 Email email_addr	string	Required	Contact Email. e.g. "john@example.com"
Tags tags	string	Required	Comma-separated tag names

Sample request

{
  "email_addr": "john@example.com",
  "tags": "e.g. vip, enterprise"
}

Returns

{
  "id": 123,
  "tags": [
    "vip",
    "enterprise"
  ]
}

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

FAQ

Questions about Add Tag to Contact.

What does the Add Tag to Contact action do in Agile CRM?

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.

What inputs does Add Tag to Contact require?

Required: Contact Email, Tags. 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 Add Tag to Contact support batch operations?

Yes. Run Add Tag to 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