Create Company or Associated Contact Workflow Action in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Create Company or Associated Contact action lets a Sparkforge workflow create a new Company record — or a Contact tied to an existing Company — using mapped values from webhooks, forms, or contact fields.

The Create Company or Associated Contact action is a workflow step in Sparkforge that creates new Company records or adds Contacts under an existing Company. It runs on incoming data from forms, webhooks, or other workflow triggers, so you stop typing the same B2B records into the CRM by hand.

What This Action Does

  • Creates a new Company record from inside a workflow.
  • Creates a Contact and links it to the Company that triggered the workflow.
  • Maps field values dynamically from inbound webhooks, form submissions, or fixed text.
  • Keeps Company-to-Contact associations clean without manual record creation.

Action Configuration

1. Object Record to Create

Pick what the action creates:

  • Company — a new Company record.
  • Associated Contact — a new Contact linked to the workflow's current Company.

2. Field Mapping

Map workflow data or fixed values to the fields you want populated. Examples:

  • Company Name → {{inboundWebhookRequest.body.company}}
  • Contact Email → {{inboundWebhookRequest.body.email}}
  • First Name → {{inboundWebhookRequest.body.first_name}}

3. Dynamic Value Sources

You can map from:

  • Inbound webhook payloads (e.g., {{inboundWebhookRequest.body.companyName}})
  • Company fields (when a company event triggers the workflow)
  • Fixed text values (e.g., "Sparkforge Partners")
  • Custom Values

4. Association Behavior

When you choose Associated Contact, the new contact is automatically linked to the Company record that triggered the workflow. The link shows up under that Company's Associated Contacts section.

5. Save

Click + Add Field for additional mappings, then Save Action. The workflow creates the record and populates all mapped fields on each run.

Example: Create a Company From a Webhook

Goal: Auto-create a Company when a new B2B lead hits the webhook.

  • Workflow Type: Company-based
  • Trigger: Inbound Webhook
  • Object Record to Create: Company
  • Mappings: Company Name → {{inboundWebhookRequest.body.companyName}}, Domain → {{inboundWebhookRequest.body.domain}}, Industry → {{inboundWebhookRequest.body.industry}}

The webhook fires, the workflow runs, and a Company is created in the CRM with all mapped fields.

Example: Add an Associated Contact to a Company

Goal: Add an employee Contact under an existing Company record.

  • Workflow Type: Company-based
  • Trigger: Company Updated or Inbound Webhook
  • Object Record to Create: Associated Contact
  • Mappings: First Name, Last Name, Email, Job Title from the webhook payload

The new Contact lands in the CRM and shows up under the parent Company's Associated Contacts.

Frequently Asked Questions

What is the difference between Create and Update?
Create makes new Company or Contact records. Update modifies existing ones. Use Update when the record already exists in your CRM.
What workflow types support this action?
Company-based workflows. The action references the Company that triggers the workflow when associating a new Contact.
Will this create duplicate Companies?
It will create a new record on every run unless you add deduplication logic upstream. Match on company name or domain before this step if duplicates are a concern.
Where can dynamic values come from?
Inbound webhook payloads, Company fields from the trigger, fixed text strings, and Custom Values.
Where do I see the new associations after the action runs?
On the Company record's Associated Contacts panel and on the Contact record's Associated Companies panel.

Was this article helpful?