Create Contact: ActiveCampaign 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
Email email	string	Required	Email. e.g. "user@example.com"
First Name firstName	string	Optional	First Name. e.g. "John"
Last Name lastName	string	Optional	Last Name. e.g. "Doe"
Phone phone	string	Optional	Phone. e.g. "+15551234567"

Sample request

{
  "email": "user@example.com",
  "firstName": "John",
  "lastName": "Doe",
  "phone": "+15551234567"
}

Returns

{
  "contact": {
    "id": "123",
    "email": "user@example.com",
    "lastName": "Doe",
    "firstName": "John"
  }
}

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

FAQ

Questions about Create Contact.

What does the Create Contact action do in ActiveCampaign?

Creates a new contact with email, name, phone, and any configured custom fields. ActiveCampaign treats email as the dedupe key — repeated creates with the same email update the existing record. For "auto-add new leads from upstream" workflows, this is the entry point.

What inputs does Create Contact require?

Required: Email. 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 ActiveCampaign 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 Create Contact support batch operations?

Yes. Run Create Contact inside a Loop node to process arrays. Tiny Command handles ActiveCampaign's rate limits automatically so you don't have to throttle manually.

More actions