Short answer: Drop the "HubSpot → 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 |
|---|---|---|---|
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" |
Company company | string | Optional | Company. e.g. "Acme Inc" |
Job Title jobtitle | string | Optional | Job Title. e.g. "VP of Engineering" |
Lifecycle Stage lifecyclestage | options | Optional | Lifecycle Stage. Options: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist |
{"email": "user@example.com","firstname": "John","lastname": "Doe","phone": "+15551234567","company": "Acme Inc"}
{"id": "501","properties": {"email": "user@example.com","lastname": "Doe","firstname": "John","createdate": "2025-01-15T12:00:00.000Z"}}
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.