Connect Zendesk to Parabola

Pull Zendesk tickets, users, organizations, ticket comments, and CSAT data into Parabola to automate support reporting, SLA tracking, and CX analytics.

Zendesk is a customer service platform used by support teams to manage tickets, customer profiles, and CSAT across email, chat, phone, and social. Connecting Zendesk to Parabola lets ops, CX, and analytics teams pull tickets, users, and organizations into the same flows used for orders, billing, and CRM data, without manual exports or custom ETL.

Pull from Zendesk

The Pull from Zendesk step retrieves tickets and related records from your Zendesk account so you can build dashboards, reconcile support data with the rest of the business, and trigger alerts on volume or SLA conditions.

How to authenticate

Zendesk uses Basic Auth with an API token plus your account subdomain.

Generate a Zendesk API token

1. Log in to Zendesk as an administrator.

2. Open Admin Center in the sidebar, then go to Apps and integrations → APIs → Zendesk API.

3. In the API tokens section, click Add API Token.

4. Add a description like “Parabola integration” and copy the token. The full token only shows once — store it somewhere secure before closing the window.

Connect in Parabola

1. Add a Pull from Zendesk step to your flow and click Authorize.

2. Enter your Zendesk subdomain (for acme.zendesk.com it’s acme), your admin email, and the API token.

3. Pick the resource you want (Tickets, Users, Organizations) and configure filters like date range or status.

Available data

The Pull from Zendesk step covers the resources most support teams need for reporting. For anything not exposed in the dropdown, use a Pull from an API step pointed at the Zendesk REST API with the same credentials.

• Tickets — status, priority, assignee, requester, description, tags, custom fields, timestamps, and satisfaction ratings.
• Users — customer and agent profiles: names, emails, roles, organization, time zone, custom user fields.
• Organizations — company profiles with domains, notes, tags, and custom organization fields.
• Groups — agent teams and memberships used for routing and assignment.
• Ticket comments — public and private comments on tickets, with attachments and author details.
• Ticket audits — change history showing what changed on a ticket, when, and by whom.
• Ticket forms — custom forms used for different ticket types.
• Ticket fields — system and custom field definitions for mapping IDs to display names.
• Tags — labels applied to tickets, users, and organizations.
• Triggers, automations, macros, views — the rules and saved queries that drive your support workflow.

Common use cases

• Track team performance and SLAs: Pull tickets with first-response and resolution timestamps, calculate per-agent and per-team metrics, and drop the result into Google Drive, Smartsheet, or a Slack summary for the morning standup.
• Tie support volume to orders: Join Zendesk tickets with order data from Shopify, Amazon Seller Central, or Squarespace on customer email to surface which products and SKUs drive the most support load.
• Reconcile support with billing: Join Zendesk organizations with billing data from Stripe or QuickBooks Online to weight ticket volume by ARR and prioritize escalations on top accounts.
• Cross-system CX dashboard: Combine Zendesk with shipping data from DHL, FedEx, or AfterShip to find where late deliveries turn into tickets, then push the rollup to a warehouse like Snowflake or BigQuery.
• Tie tickets to engineering work: Match Zendesk tickets with Jira issues on a custom field to see which customer-facing tickets are blocked on engineering, and post a status update to Slack.
• Send escalation alerts: Filter to high-priority or SLA-breached tickets, enrich with order or account context, and notify on-call via Slack or Twilio SMS.

Tips for using Parabola with Zendesk

• Filter by date in the step. A multi-year Zendesk account holds a lot of tickets. Pull “tickets updated in the last 7 days” and let downstream steps handle aggregations.
• Pull tickets, comments, and audits separately. They live in three endpoints. Most reporting flows need at least tickets plus one of the others. Join on ticket_id.
• Map ticket-field IDs to names. Custom field values come back keyed by numeric ID. Pull Ticket fields once, join on field ID, and rename columns so reports are readable.
• Match cadence to use case. Hourly for live ops dashboards and peak-season monitoring, daily for performance reports, weekly for CSAT trend analysis. The same flow can run on different schedules across forks.
• Normalize tags and groups. Tags and group memberships are arrays. Use Stack columns to one-row-per-tag before grouping, or flatten with Edit columns for downstream joins.
• Add Checks and Alerts. Set thresholds for ticket volume, response time, CSAT, and unassigned queue depth. Parabola can ping Slack or email when output crosses a limit.

FAQ

Can I push data back into Zendesk?

The Pull from Zendesk step is read-only. To create or update tickets, post comments, or update users, use a Send to an API step pointed at the Zendesk REST API with the same email + API token Basic Auth.

How do I pull only recent tickets?

Use the date filter inside the Pull from Zendesk step, or pull broadly and add a Filter rows step on updated_at. For live monitoring, schedule the flow every 15–30 minutes and filter to “last 1 hour” so each run stays small.

Can I pull from multiple Zendesk subdomains in one flow?

Yes. Add multiple Pull from Zendesk steps and authorize each one with a different subdomain and API token, then union the results downstream.

How do I report CSAT by agent or product?

Pull Tickets with satisfaction_rating included, plus Users for agent details. Join tickets to agents on assignee_id. For product breakdowns, join the result to order data from Shopify on customer email or order number.

---

With Zendesk and Parabola connected, the support reports, SLA dashboards, and ticket-to-order reconciliations your team rebuilds every Monday run on a schedule with clean output flowing into the tools where your team actually works.