AActionAgile CRMUpdated September 2026
How do I delete a contact from Agile CRM?
Short answer: You can delete contact in Agile CRM by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Agile CRM Delete Contact 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.
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
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Delete Contact.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Delete Contact.
What does the Delete Contact action do in Agile CRM?
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.
What inputs does Delete 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 run history shows the failed step with its input and the error message Agile CRM returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Delete Contact support batch operations?
Run Delete Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Agile CRM's rate limits.
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.
ActionGet 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.
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.