Create Organization: Zendesk 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
Organization Name name	string	Required	Organization Name
Notes notes	string	Optional	Notes
Domain Names domain_names	string	Optional	Comma-separated domain names

Sample request

{
  "name": "{{trigger.name}}",
  "notes": "{{trigger.notes}}",
  "domain_names": "e.g. example.com, example.org"
}

Returns

{
  "organization": {
    "id": 456,
    "name": "Acme Corp",
    "domain_names": [
      "acme.com"
    ]
  }
}

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

FAQ

Questions about Create Organization.

What does the Create Organization action do in Zendesk?

Creates an organization (B2B account) in Zendesk with name, domains, tags, and custom fields. Used to mirror CRM accounts into Zendesk so end-users auto-link by email domain.

What inputs does Create Organization require?

Required: Organization Name. 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 Zendesk 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 Organization support batch operations?

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

More actions