Short answer: Drop the "Agile CRM → Create Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
First Name first_name | string | Required | First Name. e.g. "John" |
Last Name last_name | string | Optional | Last Name. e.g. "Doe" |
Email email | string | Required | Email. e.g. "john@example.com" |
Phone phone | string | Optional | Phone. e.g. "+15551234567" |
Company company | string | Optional | Company. e.g. "Acme Inc" |
Tags tags | string | Optional | Comma-separated tags |
{"first_name": "John","last_name": "Doe","email": "john@example.com","phone": "+15551234567","company": "Acme Inc"}
{"id": 123456,"tags": ["lead"],"properties": [{"name": "first_name","value": "John"},{"name": "email","value": "john@example.com"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.