Upsert Company: Intercom 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
Company Name name	string	Required	Company Name
Company ID company_id	string	Required	Your unique company identifier
Plan plan	string	Optional	Plan
Industry industry	string	Optional	Industry

Sample request

{
  "name": "{{trigger.name}}",
  "company_id": "{{trigger.company_id}}",
  "plan": "{{trigger.plan}}",
  "industry": "{{trigger.industry}}"
}

Returns

{
  "id": "abc",
  "name": "Acme Inc",
  "type": "company",
  "company_id": "123"
}

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

FAQ

Questions about Upsert Company.

What does the Upsert Company action do in Intercom?

Creates a new company in Intercom or updates an existing one (upsert by company_id). Companies are how Intercom groups users into B2B accounts.

What inputs does Upsert Company require?

Required: Company Name, Company ID. 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 Intercom 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 Upsert Company support batch operations?

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

More actions