Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Zendesk

Connect Zendesk with Flows360 to automate support workflows and keep service data in sync.

CategorySupport
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Zendesk with Flows360

Connect Zendesk with Flows360 to automate support workflows and keep service data in sync.

Use the Zendesk connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 18 actions and 10 triggers.

Available actions

  • Create Ticket
  • Update Ticket
  • Add Tag to Ticket
  • Remove Tag(s) from Ticket
  • Attach File to Ticket
  • Add Comment to Ticket
  • Create Organization
  • Update Organization
  • Plus 10 additional declared actions.

Available triggers

  • New ticket in view
  • New Ticket
  • Updated Ticket
  • Tag Added to Ticket
  • New Organization
  • New User
  • Plus 4 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Zendesk
  • Package: @activepieces/piece-zendesk@0.3.0
  • Exact artifact digest: sha256:65c2cf610bc8ed48407d4f3281ec65888474fbb54b18a53815ce754f547808e7
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Ticket (create-ticket), Create a new ticket in Zendesk. Classification: read.
  • Update Ticket (update-ticket), Modify ticket fields or status via API call. Classification: read.
  • Add Tag to Ticket (add-tag-to-ticket), Apply one or more tags to a ticket. Classification: read.
  • Remove Tag(s) from Ticket (remove-tag-from-ticket), Remove one or more tags from a ticket. Classification: read.
  • Attach File to Ticket (attach-file-to-ticket), Attach a file to a ticket. Classification: read.
  • Add Comment to Ticket (add-comment-to-ticket), Append a public/private comment to a ticket. Classification: read.
  • Create Organization (create-organization), Create a new organization record. Classification: read.
  • Update Organization (update-organization), Update existing organization fields. Classification: read.
  • Create User (create-user), Add a new user to the Zendesk instance. Classification: read.
  • Delete User (delete-user), Remove a user and associated records from the account. Classification: read.
  • Find Organization(s) (find-organization), Search organizations by name, domain, external ID, or other criteria. Classification: read.
  • Find Ticket(s) (find-tickets), Search tickets by ID, field, or content. Classification: read.
  • Find User(s) (find-user), Search users by email, name, role, or other criteria. Classification: read.
  • Find an Agent (find-agent), Find an agent by email or name. Classification: read.
  • Find a Group (find-group), Find a group by name. Classification: read.
  • Find Latest Comment (find-latest-comment), Find the latest comment on a ticket. Classification: read.
  • Update User (update-user), Update existing user fields. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New ticket in view, polling.
  • New Ticket, webhook.
  • Updated Ticket, webhook.
  • Tag Added to Ticket, webhook.
  • New Organization, webhook.
  • New User, webhook.
  • New Suspended Ticket, webhook.
  • New Action on Ticket, webhook.
  • New Group, polling.
  • Tag Added to User, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects28
Supported actionsNot published
Triggers10

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Agent Email Required
  • Token Required · protected credential
  • Organization (e.g activepieceshelp) Required

Supported objects

ObjectReadWriteNotes
Create Ticket Yes No Create a new ticket in Zendesk.
Update Ticket Yes No Modify ticket fields or status via API call.
Add Tag to Ticket Yes No Apply one or more tags to a ticket.
Remove Tag(s) from Ticket Yes No Remove one or more tags from a ticket.
Attach File to Ticket Yes No Attach a file to a ticket.
Add Comment to Ticket Yes No Append a public/private comment to a ticket.
Create Organization Yes No Create a new organization record.
Update Organization Yes No Update existing organization fields.
Create User Yes No Add a new user to the Zendesk instance.
Delete User Yes No Remove a user and associated records from the account.
Find Organization(s) Yes No Search organizations by name, domain, external ID, or other criteria.
Find Ticket(s) Yes No Search tickets by ID, field, or content.
Find User(s) Yes No Search users by email, name, role, or other criteria.
Find an Agent Yes No Find an agent by email or name.
Find a Group Yes No Find a group by name.
Find Latest Comment Yes No Find the latest comment on a ticket.
Update User Yes No Update existing user fields.
Custom API Call Yes No Make a custom API call to a specific endpoint
New ticket in view Yes No polling trigger declared by the pinned package.
New Ticket Yes No webhook trigger declared by the pinned package.
Updated Ticket Yes No webhook trigger declared by the pinned package.
Tag Added to Ticket Yes No webhook trigger declared by the pinned package.
New Organization Yes No webhook trigger declared by the pinned package.
New User Yes No webhook trigger declared by the pinned package.
New Suspended Ticket Yes No webhook trigger declared by the pinned package.
New Action on Ticket Yes No webhook trigger declared by the pinned package.
New Group Yes No polling trigger declared by the pinned package.
Tag Added to User Yes No webhook trigger declared by the pinned package.

Triggers

New ticket in view · Poll

Triggers when a new ticket is created in a view

Inputs

  • view_id · string
New Ticket · Webhook

Fires when a new ticket is created (optionally filtered by organization). Requires a Zendesk Trigger with Notify active webhook.

Inputs

  • organization_id · string
Updated Ticket · Webhook

Fires when an existing ticket is updated. Requires a Zendesk Trigger with Notify active webhook.

Inputs

  • organization_id · string
Tag Added to Ticket · Webhook

Fires when a ticket update includes the specified tag. Requires a Zendesk Trigger with Notify active webhook.

Inputs

  • specific_tag · string
New Organization · Webhook

Fires when a new organization record is created. Uses Zendesk event webhook (no Trigger needed).

New User · Webhook

Fires when a new user is created. Uses Zendesk event webhook (no Trigger needed).

Inputs

  • user_role · string
New Suspended Ticket · Webhook

Fires when a ticket is suspended. Requires a Zendesk Trigger with Notify active webhook. Suspended tickets auto-delete after 14 days.

Inputs

  • organization_filter · string
New Action on Ticket · Webhook

Fires when the specified ticket updates. Requires a Zendesk Trigger with Notify active webhook.

Inputs

  • ticket_id · number
New Group · Poll

Fires when a new group is created.

Tag Added to User · Webhook

Triggers when one or more tags are added to a user.

Setup

Setup

  1. Add the Zendesk connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Agent Email (email), required.
  • Token (token), required; stored as a sensitive connection value.
  • Organization (e.g activepieceshelp) (subdomain), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-zendesk@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 18 actions and 10 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Zendesk connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-zendesk@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com