Update Contact
Automatically set or overwrite Orbit contact fields as part of a workflow. Use static values you define, or pull data dynamically from prior steps like form submissions, enrichment, or AI nodes.
Overview
The Update Contact node lives in the Automations category of the workflow editor. When a workflow runs, this node finds the contact by email and updates the fields you configure.
This is useful when you want to enrich your contact records with data that flows through the workflow — for example, setting a company name from a Clay enrichment step, updating a job title from a form field, or marking a status based on AI qualification results.
Plan requirement
The Update Contact node is available on Pro plans and above.
Adding the Node
- Open a workflow in the editor and click the + Add Node button.
- Find the Automations category.
- Click Update Contact to add it to the canvas.
- Connect it to the node that should run before it (e.g., a trigger, filter, or enrichment node).
Available Contact Fields
Each mapping targets one of these Orbit contact fields. You can add multiple mappings in a single node — one per field.
| Field | Key | Description |
|---|---|---|
| First Name | first_name | The contact's first name |
| Last Name | last_name | The contact's last name |
| Phone | phone | Phone number |
| Company | company | Company or organization name |
| Job Title | job_title | The contact's role or title |
| Status | status | Contact status label (e.g. Lead, Customer) |
Configuring Field Mappings
Click the Update Contact node on the canvas to open the configuration panel. For each field you want to set, add a mapping with three parts:
Pick a Contact Field
Select which Orbit contact field to update (e.g., First Name, Company, Status). Each field can only be mapped once per node.
Choose a Value Source
Decide where the value comes from:
Set the Value
Enter a static string, or select a field from the dropdown. The dropdown lists every field available from nodes upstream of this step.
Click + Add Field Mapping to add more mappings to the same node, then click Save.
Example Use Cases
Set company name from Clay enrichment
After a Clay enrichment step, map the enriched company name to the contact's Company field.
Contact Field: Company
Source: From Prior Step → Company Name (from Clay)
Update status after AI qualification
After an SDR Qualifying agent runs, set the contact's status to the AI bucket name.
Contact Field: Status
Source: From Prior Step → Qualification Bucket (from SDR Agent)
Set a static status for all contacts from a specific form
Tag every contact from a demo request form with a fixed status value.
Contact Field: Status
Source: Static Value → Demo Request
Populate name and phone from a form submission
Pull the first name, last name, and phone fields from the form trigger into the contact record.
Contact Field: First Name ← first_name (form field)
Contact Field: Last Name ← last_name (form field)
Contact Field: Phone ← phone (form field)
How It Works at Runtime
- The workflow identifies the contact by the email address in the submission data.
- For each mapping, the node resolves the value — either from the static string or by looking up the referenced field in the workflow's combined data.
- If the resolved value differs from the current contact value, the field is updated.
- Every change is logged in the contact's edit history with a "workflow_automation" source so you can trace what changed and why.
- If no values changed (e.g., all fields already match), the node succeeds with zero updates.
Tips
- Place the Update Contact node after enrichment or AI nodes so their output fields are available in the "From Prior Step" dropdown.
- You can combine static and dynamic values in the same node — for example, set Status to a fixed string and Company from enrichment.
- Use the Run History panel to verify which fields were updated after a workflow run.
- Incomplete field mappings are automatically removed on save, so only fully configured mappings are persisted.
Did this answer your question?