Start free
ActionZendeskUpdated June 2026

How do I list Zendesk organizations?

Short answer: You can list organizations in Zendesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Zendesk List Organizations action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Organizations in Zendesk — start free All 17 Zendesk actions
List Organizations in Zendesk — start free
Sample request
{}
Returns
{
  "count": 1,
  "organizations": [
    {
      "id": 456,
      "name": "Acme Corp",
      "domain_names": [
        "acme.com"
      ]
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List Organizations.

Any of these apps can fire this action as part of a workflow.

Gmail → Zendesk
1 Gmail triggers
Slack → Zendesk
13 Slack triggers
Google Sheets → Zendesk
2 Google Sheets triggers
HubSpot → Zendesk
18 HubSpot triggers
FAQ

Questions about List Organizations.

What does the List Organizations action do in Zendesk?
Lists organizations in Zendesk with their domains and tags. Used for B2B account-level reporting and CRM sync.
What inputs does List Organizations require?
List Organizations has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List Organizations support batch operations?
Yes. Run List Organizations inside a Loop node to process arrays. TinyCommand handles Zendesk's rate limits automatically so you don't have to throttle manually.
More actions

Other Zendesk actions.

Action
Add Comment to Ticket
Adds a public comment (customer-visible) or internal note to an existing Zendesk ticket. Used for AI summary notes, automated status broadcasts, or piping context from external systems.
Action
Create Organization
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.
Action
Create Ticket
Creates a new support ticket in Zendesk with requester, subject, comment body, priority, status, type, group, assignee, and tags. The entry point for converting external alerts or forms into trackable tickets.
Action
Create User
Creates a new user (customer or agent) in Zendesk with name, email, role, organization, and tags. Used to provision users before ticket creation or to mirror your auth system.
Action
Delete Ticket
Permanently deletes a Zendesk ticket by ID. Two-step: this marks it deleted; for PII purposes you may also need to "redact" comments separately.
Action
Delete User
Deletes a user from Zendesk by ID. Two-step: soft-delete first; pass permanently=true (or use the dedicated permanently-delete endpoint) for GDPR right-to-delete.
List Organizations in Zendesk — start free