Zendesk Connector
Description
Zendesk is a company headquartered in San Francisco, California. It provides software-as-a-service products related to customer support, sales, and other customer communications. The Zendesk component allows managing Users and Tickets inside a Zendesk domain.
API Documentation
This component was built using the Zendesk API Reference.
Zendesk webhooks
The Zendesk API supports two types of webhooks - one for when something has changed for a user or an organization, and one when something has changed on a support ticket.
Zendesk user and support webhooks
To be alerted when a change to a user or organization has occurred, create a new webhook using the Create Webhook action.
Select the events that will cause the webhook to fire.
For example, selecting the zen:event-type:user.deleted event will cause the webhook to fire whenever a user is deleted.
A full list of webhook event types are available in the Zendesk developer docs.
Zendesk ticket webhooks
To be alerted when a ticket has changed, first create a webhook using the Create Webhook action.
When selecting webhook events, choose conditional_ticket_events (and only that value).
This will create a webhook, pointed at an integration flow, that can be triggered conditionally.
Next, a trigger must be created that will send data via the webhook just created. Fetch the webhook's id from the step where the webhook was created, and feed it into a Create Webhook Trigger action. The default conditional and webhook body values will cause the webhook to be triggered whenever a ticket is changed, and will send all data related to the ticket to the webhook. Keeping the default values is recommended. The conditions under which the trigger fires can be changed - see the Zendesk conditions reference for details.
Connections
API Token
key: apiTokenTo use the API Token connection for Zendesk, provide the following parameters:
Configure the Connection
- For Username enter the email of the Zendesk account.
- For API Token enter the generated API Token under Admin Center (
https://YOUR-DOMAIN-HERE.zendesk.com/admin/home) -> App and Registrations -> Zendesk API -> Token access. - For Zendesk Sub Domain enter the Zendesk sub domain. The subdomain can be found inside of the Zendesk URL:
https://YOUR-DOMAIN-HERE.zendesk.com/
| Input | Notes | Example |
|---|---|---|
| API Token | The API token generated in Zendesk. | your-api-token |
| Zendesk Domain | https://{{#zendeskDomain}}.zendesk.com | |
| Username | The Zendesk username. This is the email address used to sign in to Zendesk. | john.doe@example.com |
| Zendesk Sub Domain | The Zendesk sub domain. For example, if the Zendesk URL is https://acme-inc.zendesk.com, the sub domain is acme-inc. | acme-inc |
OAuth 2.0 (Deprecated)
key: oauth2The Zendesk component authenticates requests with OAuth 2.0. This connection (OAuth 2.0 (Deprecated)) is retained for backward compatibility; new connections should use OAuth 2.0 (oauth2DynamicInputs).
Setup Steps
To configure an application inside Zendesk follow the directions in this guide. Then, create a new Zendesk connection.
Configure the Connection
- For Client ID enter the unique identifier of the app inside the Zendesk admin dashboard.
- For Client Secret enter the generated client secret received from the Zendesk admin dashboard.
- For Redirect URL/Callback URL in the Zendesk app settings, enter
https://oauth2.prismatic.io/callback. - For Authorize URL enter
https://YOUR-ZENDESK-DOMAIN.zendesk.com/oauth/authorizations/new, replacing the placeholder with the Zendesk sub domain. - For Token URL enter
https://YOUR-ZENDESK-DOMAIN.zendesk.com/oauth/tokens, replacing the placeholder with the Zendesk sub domain. - For Scopes refer to the guide linked above. It contains detailed information on picking the correct scope.
The sub domain used in both URLs above can be found inside the Zendesk URL: https://YOUR-ZENDESK-DOMAIN.zendesk.com/
| Input | Notes | Example |
|---|---|---|
| Authorize URL | The OAuth 2.0 Authorization URL for Zendesk. | https://acme-inc.zendesk.com/oauth/authorizations/new |
| Client ID | The Client ID of the OAuth application registered in Zendesk. | |
| Client Secret | The Client Secret of the OAuth application registered in Zendesk. | |
| Scopes | A space-delimited set of one or more scopes to get the user's permission to access. | read write |
| Token URL | The OAuth 2.0 Token URL for Zendesk. | https://acme-inc.zendesk.com/oauth/tokens |
OAuth 2.0
key: oauth2DynamicInputsThe Zendesk component authenticates requests with OAuth 2.0.
Setup Steps
To configure an application inside Zendesk follow the directions in this guide. Then, create a new Zendesk connection.
Configure the Connection
- For Zendesk Sub Domain enter the Zendesk sub domain (e.g. if the Zendesk URL is
https://acme-inc.zendesk.com, then the sub domain isacme-inc). - For Client ID enter the unique identifier of the app inside the Zendesk admin dashboard.
- For Client Secret enter the generated client secret received from the Zendesk admin dashboard.
- For Redirect URL/Callback URL in the Zendesk app settings, enter
https://oauth2.prismatic.io/callback. - For Scopes refer to the guide linked above. It contains detailed information on picking the correct scope.
| Input | Notes | Example |
|---|---|---|
| Authorize URL | The OAuth 2.0 Authorization URL for Zendesk. | https://{{#domain}}.zendesk.com/oauth/authorizations/new |
| Client ID | The Client ID of the OAuth application registered in Zendesk. | |
| Client Secret | The Client Secret of the OAuth application registered in Zendesk. | |
| Zendesk Sub Domain | The Zendesk sub domain. For example, if the Zendesk URL is https://acme-inc.zendesk.com, the sub domain is acme-inc. | acme-inc |
| Scopes | A space-delimited set of one or more scopes to get the user's permission to access. | read write |
| Token URL | The OAuth 2.0 Token URL for Zendesk. | https://{{#domain}}.zendesk.com/oauth/tokens |
Triggers
New and Updated Tickets
Retrieves existing and ongoing tickets from Zendesk. Load history once, check for changes on a schedule, or both. | key: pollChangesTrigger
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. | |
| Look-back Date | The date the initial sync starts from, in YYYY-MM-DD format. Cannot be a future date. Leave empty to start from the first recurrence with no backfill. When set, the initial sync seeds each ticket created or updated on or after this date once, ignoring the visibility filters. | 2026-01-01 |
| Show New Records | When true, newly created tickets are included in the trigger output. | true |
| Show Updated Records | When true, tickets updated since the last poll are included in the trigger output. | true |
The New and Updated Tickets polling trigger checks Zendesk on a configured schedule for tickets that were created or modified since the last poll. Unlike webhook-based triggers, polling does not require webhook subscription management and works reliably for low-frequency monitoring scenarios.
The trigger uses Zendesk's Incremental Tickets Export endpoint with cursor-based pagination. This guarantees that no tickets are missed between runs and avoids re-processing old data, because Zendesk returns a stable cursor that points to the exact position in the ticket change stream.
How It Works
On each scheduled execution, the trigger:
- Reads
lastPolledAtandafterCursorfrom the polling state. With no stored cursor and no Look-back Date,start_timeis set to 60 seconds before the current time, because Zendesk requiresstart_timeto be at least one minute in the past. - Calls the Zendesk Incremental Tickets Export endpoint, resuming from the persisted
afterCursorwhen available, or usingstart_timeotherwise. It reads up to ten pages per recurrence with batching off, or one page per round with batching enabled, and stops earlier if the stream ends. Stopping at the limit is not an error: the cursor it stops on is a complete resume point. With batching off the remaining pages arrive on later recurrences; with batching on the platform re-invokes the trigger from that cursor until the stream ends, within the same recurrence. - Partitions the collected tickets into
createdandupdatedbuckets by comparing each ticket'screated_atagainst thelastPolledAtcutoff. Tickets whosecreated_atis after the cutoff land increated; every other ticket the export returns lands inupdated, because the export returns a ticket only when it has changed. - Persists the new
afterCursoron every recurrence. It advanceslastPolledAtonly once the stream ends, because that value is the cutoff step 3 compares against, and moving it while pages are still outstanding would place it ahead of tickets that have not been delivered yet. It then sets it to one minute before the recurrence started, because Zendesk withholds the most recent minute of changes until a later read. - Emits the partitioned results filtered by the Show New Records and Show Updated Records toggles.
Initial sync
An initial sync seeds a complete starting state, so inputs that narrow the change feed would leave gaps in it and are ignored for its duration, while inputs that shape how tickets are fetched still apply. Set a Look-back Date to start one: it begins on the first recurrence, seeds each ticket created or modified on or after that date exactly once, and ignores Show New Records and Show Updated Records.
The window has no fixed upper bound, so a ticket modified while the sync is still draining is swept into the sync rather than left for the incremental recurrences. The trigger's position is Zendesk's own export cursor and advances page by page; when the stream ends, the trigger commits its created/updated cutoff, and every later recurrence resumes the export cursor from where the sync stopped and classifies against that cutoff, so nothing is lost. No field in the payload marks the handoff. With batching off the sync drains up to ten pages per scheduled recurrence and a large history therefore spans several of them; with batching on the platform drives the rounds and the sync drains inside one poll cycle.
The Connection applies throughout. The sync is not affected by any page-size input, because the trigger has none: its page size is fixed by the component.
Batching
Batching is enabled per flow on this trigger: each changed record is dispatched as its own execution, or grouped by the configured batch size. Batch size and batch concurrency can both be overridden per instance. Raising concurrency increases the request volume sent to Zendesk.
To turn it on, select the flow's trigger, open the Flow control tab, and switch on Enable Batching. Under Batch Size, keep Trigger default or choose Custom batch size. Batch Concurrency is optional; leave it blank for no batch-level limit.
With batching off, a downstream step reads the arrays at body.data.created and body.data.updated. With batching on those fields do not exist: each execution receives one ticket, or an array of them at a batch size above one, as { "changeType": "created" | "updated", "record": { ... } }. Any step reading the older shape must be updated before batching is enabled. Because batching is enabled per flow, the change is scoped to that flow and leaves other flows using this trigger untouched.
Returned Data
With batching off, the trigger emits a payload with two arrays, created and updated, each containing ticket resources from the Zendesk Incremental Tickets Export endpoint.
Example Payload
{
"data": {
"created": [
{
"id": 35437,
"subject": "New ticket received",
"status": "new",
"priority": "normal",
"created_at": "2026-05-20T14:00:00Z",
"updated_at": "2026-05-20T14:00:00Z",
"requester_id": 114092137191
}
],
"updated": [
{
"id": 35436,
"subject": "Re: Billing question",
"status": "open",
"priority": "high",
"created_at": "2009-07-20T22:55:29Z",
"updated_at": "2026-05-20T15:00:00Z",
"requester_id": 114092137191
}
]
}
}
With batching on, each execution receives one tagged item instead, or an array of them when the batch size is above one.
Example Batched Item
{
"changeType": "created",
"record": {
"id": 35437,
"subject": "New ticket received",
"status": "new",
"priority": "normal",
"created_at": "2026-05-20T14:00:00Z",
"updated_at": "2026-05-20T14:00:00Z",
"requester_id": 114092137191
}
}
Fields shown are representative. The full response object includes additional properties.
Example Payload for New and Updated Tickets⤓
Webhook
Receive and validate webhook requests from Zendesk for manually configured webhook subscriptions. | key: webhook
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Webhook⤓
Data Sources
Select Article Subscription
Select a subscription for an article in the Zendesk Help Center. | key: selectArticleSubscription | type: picklist
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Connection | The Zendesk connection to use. |
Example Payload for Select Article Subscription⤓
Select Articles
Select an article from the Zendesk Help Center. | key: listArticlesDataSource | type: picklist
| Input | Notes | Example |
|---|---|---|
| Locale | The locale code for the resource. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Select Articles⤓
Select Categories
Select a category from the Zendesk Help Center. | key: listCategoriesDataSource | type: picklist
| Input | Notes | Example |
|---|---|---|
| Locale | The locale code for the resource. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Select Categories⤓
Select Management Permission Groups
Select a management permission group from the Zendesk Help Center. | key: listPermissionGroupsDataSource | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Select Management Permission Groups⤓
Select Post
Select a post from the Zendesk Help Center. | key: selectPost | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Select Post⤓
Select Post Subscription
Select a subscription for a post in the Zendesk Help Center. | key: selectPostSubscription | type: picklist
| Input | Notes | Example |
|---|---|---|
| Post ID | The unique identifier for the post. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Select Post Subscription⤓
Select Section Subscription
Select a subscription for a section in the Zendesk Help Center. | key: selectSectionSubscription | type: picklist
| Input | Notes | Example |
|---|---|---|
| Section ID | The unique identifier for the section. | 123123213 |
| Connection | The Zendesk connection to use. |
Example Payload for Select Section Subscription⤓
Select Sections
Select a section from the Zendesk Help Center. | key: listSectionsDataSource | type: picklist
| Input | Notes | Example |
|---|---|---|
| Locale | The locale code for the resource. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Select Sections⤓
Select Tags
Select a tag from the Zendesk account. | key: listTagsDataSource | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Select Tags⤓
Select Ticket
Select a ticket from the Zendesk account. | key: selectTicket | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Select Ticket⤓
Select Topic
Select a topic from the Zendesk Help Center. | key: selectTopic | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Select Topic⤓
Select Topic Subscription
Select a subscription for a topic in the Zendesk Help Center. | key: selectTopicSubscription | type: picklist
| Input | Notes | Example |
|---|---|---|
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Select Topic Subscription⤓
Select User
Select a user from the Zendesk account. | key: selectUser | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Select User⤓
Select User Segments
Select a user segment from the Zendesk Help Center. | key: listUserSegmentsDataSource | type: picklist
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Select User Segments⤓
Actions
Associate Attachments to Article
Associate attachments in bulk to a single article, with a maximum of 20 attachments per request. | key: associateAttachmentsInBulkToArticle
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Attachment IDs | The list of attachment IDs to attach to the object. | |
| Locale | The locale code for the resource. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Associate Attachments to Article⤓
Create Article
Create a new article in the Help Center. | key: createArticle
| Input | Notes | Example |
|---|---|---|
| Body | The main content of the article. | Example Body |
| Title | The headline displayed for the article. | Example Title |
| Draft | When true, the article is saved as a draft instead of published. | false |
| Locale | The locale code for the resource. | en-us |
| Notify Subscribers | When false, suppresses the article creation email to subscribers. Useful when creating many articles at once. | false |
| Permission Group ID | The unique identifier for the permission group. | 15 |
| Section ID | The unique identifier for the section. | 123123213 |
| User Segment ID | The unique identifier for the user segment. | 15 |
| Connection | The Zendesk connection to use. |
Example Payload for Create Article⤓
Create Article Attachment
Create an attachment for an article in the Help Center. | key: createArticleAttachment
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| File | The File Attachment to upload. | |
| File Name | The display name to use for the uploaded file. | file.jpg |
| Inline | When true, the attachment is rendered inline within the content. | false |
| Locale | The Help Center locale used to populate the article picker. Defaults to 'en-us'. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Create Article Attachment⤓
Create Article Subscription
Create a subscription to an article in the Help Center. | key: createArticleSubscription
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Locale | The locale of the article. If not provided, the default locale is used. | |
| User ID | The ID of the user to subscribe to the article. If none provided, the API assumes the current user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for Create Article Subscription⤓
Create Category
Create a category in the Help Center. | key: createCategory
| Input | Notes | Example |
|---|---|---|
| Category Description | The descriptive text shown below the category title. | Example Description |
| Category Name | The display name of the category. | Example Category |
| Locale | The locale code for the resource. | en-us |
| Position | The position of the category to be created. | 42 |
| Connection | The Zendesk connection to use. |
Example Payload for Create Category⤓
Create Post
Create a new post in the Help Center. | key: createPost
| Input | Notes | Example |
|---|---|---|
| Content Tag IDs | The list of content tag IDs to attach to the object. | |
| Featured | When true, the post is featured prominently in the community. | false |
| Pinned | When true, the post is pinned to the top of its topic. | false |
| Notify Subscribers | When false, suppresses the article creation email to subscribers. Useful when creating many articles at once. | false |
| Details | The main body content of the post. | |
| Status | The current workflow state of the post. | |
| Title | The headline displayed for the post. | Example Title |
| Topic ID | The ID of the topic to create the post in. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Create Post⤓
Create Post Subscription
Create a post subscription in the Help Center. | key: createPostSubscription
| Input | Notes | Example |
|---|---|---|
| Post ID | The unique identifier for the post. | 12 |
| User ID | The ID of the user to subscribe to the post. If none provided, the API assumes the current user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for Create Post Subscription⤓
Create Section
Create a section in the Help Center. | key: createSection
| Input | Notes | Example |
|---|---|---|
| Category ID | The unique identifier for the category. | 12 |
| Locale | The locale code for the resource. | en-us |
| Position | The position of the section. | 42 |
| Section Description | The descriptive text shown below the section title. | Example Description |
| Section Name | The display name of the section. | Example Section |
| Connection | The Zendesk connection to use. |
Example Payload for Create Section⤓
Create Section Subscription
Create a section subscription in the Help Center. | key: createSectionSubscription
| Input | Notes | Example |
|---|---|---|
| Include Comments | When true, the subscription also includes notifications for comments. | false |
| Locale | The locale of the section. If not provided, the default locale is used. | |
| Section ID | The unique identifier for the section. | 123123213 |
| User ID | The ID of the user to subscribe to the section. If none provided, the API assumes the current user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for Create Section Subscription⤓
Create Ticket
Create a new ticket. | key: createTicket
| Input | Notes | Example |
|---|---|---|
| Assignee ID | The unique identifier for the user assigned to the ticket. | 403598029853443232 |
| Classification | Priority, status, and type of the record. | |
| External ID | The identifier for the ticket from an external system. | |
| Followers | The list of user IDs to add as followers on the ticket. | 488042375842 |
| Recipient Email | The email address of the ticket recipient. | Jane.Doe@example.com |
| Requester Email | The email address of the person requesting the ticket. | John.Doe@example-email.com |
| Requester Name | The full name of the person requesting the ticket. | John Doe |
| Requester Organization ID | The unique identifier for the organization the requester belongs to. | 488042375842 |
| Tags | The list of tags to attach to the resource. | Engineering |
| Ticket Comment Body | The plain text description used as the initial comment on the ticket, attributed to the assignee. | This is an example Comment. |
| Ticket Comment HTML Body | The HTML-formatted description used as the initial comment on the ticket, attributed to the assignee. | <p>This is an example Comment.</p> |
| Ticket Subject | The summary line shown at the top of the ticket. | This is an example ticket subject. |
| Connection | The Zendesk connection to use. |
Example Payload for Create Ticket⤓
Create Topic
Create a new topic in the Help Center. | key: createTopic
| Input | Notes | Example |
|---|---|---|
| Topic Description | The descriptive text shown below the topic title. | Example Description |
| Topic Name | The display name of the topic. | Example Topic |
| Connection | The Zendesk connection to use. |
Example Payload for Create Topic⤓
Create Topic Subscription
Create a new topic subscription in the Help Center. | key: createTopicSubscription
| Input | Notes | Example |
|---|---|---|
| Include Comments | When true, the subscription also includes notifications for comments. | false |
| Topic ID | The unique identifier for the topic. | 12 |
| User ID | The ID of the user to subscribe to the topic. If none provided, the API assumes the current user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for Create Topic Subscription⤓
Create User
Create a new user. | key: createUser
| Input | Notes | Example |
|---|---|---|
| Account Settings | Role, moderator permission, and verification state for the record. | |
| External ID | A unique identifier from another system. The API treats the ID as case sensitive — for example, "ian1" and "Ian1" are different users. | |
| Organization ID | The unique identifier for the organization. | |
| Profile Details | Alias, notes, and other descriptive attributes for the record. | |
| Email Address | The email address for the user. Must be unique within the Zendesk domain. | someone@example.com |
| Name | The full name of the user. | John Doe |
| Phone Number | The phone number associated with the user. | 15554008989 |
| Connection | The Zendesk connection to use. |
Example Payload for Create User⤓
Create Webhook
Create a webhook in Zendesk to receive notifications of changes to users, organizations, or tickets. | key: createWebhook
| Input | Notes | Example |
|---|---|---|
| Allow Duplicates? | When true, a webhook is created even if one with the same name already exists. | false |
| Callback URL | The URL of the endpoint that receives the webhook payload. | |
| Events | The list of events that trigger the webhook to fire. | |
| Webhook Name | A unique name used to identify the webhook in the Zendesk admin UI. | |
| Connection | The Zendesk connection to use. |
Example Payload for Create Webhook⤓
Create Webhook Trigger
Create a Zendesk trigger that fires a webhook. | key: createWebhookTrigger
| Input | Notes | Example |
|---|---|---|
| Allow Duplicates? | Allow a duplicate trigger with the same title to be created? | false |
| Trigger Conditions | The conditions under which this trigger will fire. Leave the default to fire under any change. | |
| Connection | The Zendesk connection to use. | |
| Webhook Message Body | The body to send to the webhook. See Zendesk Support documentation for placeholder references. | |
| Trigger Name | The name shown for the trigger in the Zendesk admin UI. | |
| Webhook ID | The unique identifier for the webhook this trigger fires. | 01GK7R2DBS16XB76SPDEXAMPLE |
Example Payload for Create Webhook Trigger⤓
Delete Article Attachment
Delete an existing article attachment. | key: deleteArticleAttachment
| Input | Notes | Example |
|---|---|---|
| Article Attachment ID | The unique identifier for the article attachment. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Article Attachment⤓
Delete Article Subscription
Delete a subscription to an article in the Help Center. | key: deleteArticleSubscription
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Locale | The locale of the article. If not provided, the default locale is used. | |
| Subscription ID | The unique identifier for the subscription. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Article Subscription⤓
Delete Category
Delete a category in the Help Center. | key: deleteCategory
| Input | Notes | Example |
|---|---|---|
| Category ID | The unique identifier for the category. | 12 |
| Locale | The Help Center locale used to populate the category picker. Defaults to 'en-us'. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Category⤓
Delete Instance Webhooks
Delete all webhooks pointing to this instance. | key: deleteInstanceWebhooks
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for Delete Instance Webhooks⤓
Delete Post
Delete a post in the Help Center. | key: deletePost
| Input | Notes | Example |
|---|---|---|
| Post ID | The unique identifier for the post. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Post⤓
Delete Post Subscription
Delete a post subscription in the Help Center. | key: deletePostSubscription
| Input | Notes | Example |
|---|---|---|
| Post ID | The unique identifier for the post. | 12 |
| Subscription ID | The unique identifier for the subscription. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Post Subscription⤓
Delete Section
Delete a section in the Help Center. Deleting a section also deletes all of its articles. | key: deleteSection
| Input | Notes | Example |
|---|---|---|
| Locale | The locale code for the resource. | en-us |
| Section ID | The unique identifier for the section. | 123123213 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Section⤓
Delete Section Subscription
Delete a section subscription in the Help Center. | key: deleteSectionSubscription
| Input | Notes | Example |
|---|---|---|
| Locale | The Help Center locale used to populate the section picker. Defaults to 'en-us'. | en-us |
| Section ID | The unique identifier for the section. | 123123213 |
| Subscription ID | The unique identifier for the subscription. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Section Subscription⤓
Delete Ticket
Delete a ticket by ID. | key: deleteTicket
| Input | Notes | Example |
|---|---|---|
| Ticket ID | The unique identifier for the ticket. | 12345 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Ticket⤓
Delete Topic
Delete a topic from the Help Center. | key: deleteTopic
| Input | Notes | Example |
|---|---|---|
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Topic⤓
Delete Topic Subscription
Delete a topic subscription in the Help Center. | key: deleteTopicSubscription
| Input | Notes | Example |
|---|---|---|
| Subscription ID | The unique identifier for the subscription. | 12 |
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Topic Subscription⤓
Delete User
Delete a user by ID. | key: deleteUser
| Input | Notes | Example |
|---|---|---|
| User ID | The unique identifier for the user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for Delete User⤓
Delete Webhook
Delete a webhook by ID. | key: deleteWebhook
| Input | Notes | Example |
|---|---|---|
| Webhook ID | The unique identifier for the webhook to delete. | 01GK59HW1XMB8WVZ43RPVAPXRM |
| Connection | The Zendesk connection to use. |
Example Payload for Delete Webhook⤓
Get Article
Get an article from the Help Center. | key: showArticle
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Locale | The locale of the articles to retrieve. Defaults to 'en-us'. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Get Article⤓
Get Article Attachment
Get the properties of an attachment on an article in the Help Center. | key: getArticleAttachment
| Input | Notes | Example |
|---|---|---|
| Article Attachment ID | The unique identifier for the article attachment. | 12 |
| Article ID | The unique identifier for the article. | 123123213 |
| Locale | The Help Center locale used to populate the article picker. Defaults to 'en-us'. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Get Article Attachment⤓
Get Article Subscription
Get an article subscription from the Help Center. | key: getArticleSubscription
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Locale | The locale of the article. If not provided, the default locale is used. | |
| Subscription ID | The unique identifier for the subscription. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Article Subscription⤓
Get Category
Get a category from the Help Center. | key: getCategory
| Input | Notes | Example |
|---|---|---|
| Category ID | The unique identifier for the category. | 12 |
| Locale | The locale code for the resource. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Get Category⤓
Get Post
Get a post from the Help Center. | key: getPost
| Input | Notes | Example |
|---|---|---|
| Post ID | The unique identifier for the post. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Post⤓
Get Post Subscription
Get a post subscription from the Help Center. | key: getPostSubscription
| Input | Notes | Example |
|---|---|---|
| Post ID | The unique identifier for the post. | 12 |
| Subscription ID | The unique identifier for the subscription. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Post Subscription⤓
Get Section
Get a section from the Help Center. | key: getSection
| Input | Notes | Example |
|---|---|---|
| Locale | The locale code for the resource. | en-us |
| Section ID | The unique identifier for the section. | 123123213 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Section⤓
Get Section Subscription
Get a section subscription from the Help Center. | key: getSectionSubscription
| Input | Notes | Example |
|---|---|---|
| Locale | The Help Center locale used to populate the section picker. Defaults to 'en-us'. | en-us |
| Section ID | The unique identifier for the section. | 123123213 |
| Subscription ID | The unique identifier for the subscription. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Section Subscription⤓
Get Ticket
Get a ticket by ID. | key: showTicket
| Input | Notes | Example |
|---|---|---|
| Ticket ID | The unique identifier for the ticket. | 12345 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Ticket⤓
Get Ticket By External ID
Get a ticket by external ID. | key: getByExternalId
| Input | Notes | Example |
|---|---|---|
| External ID | The identifier for the ticket from an external system. | |
| Connection | The Zendesk connection to use. |
Example Payload for Get Ticket By External ID⤓
Get Topic
Get a topic from the Help Center. | key: getTopic
| Input | Notes | Example |
|---|---|---|
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Topic⤓
Get Topic Subscription
Get a topic subscription from the Help Center. | key: getTopicSubscription
| Input | Notes | Example |
|---|---|---|
| Subscription ID | The unique identifier for the subscription. | 12 |
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Get Topic Subscription⤓
Get User
Get a user by ID. | key: showUser
| Input | Notes | Example |
|---|---|---|
| User ID | The unique identifier for the user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for Get User⤓
List Article Attachments
List all attachments for an article in the Help Center. | key: listArticleAttachments
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Fetch All | When true, automatically fetches all pages of results instead of returning a single page. | false |
| Locale | The Help Center locale used to populate the article picker. Defaults to 'en-us'. | en-us |
| Page Limit | The number of results to return per page. The maximum is 100; any greater value is capped at 100. | 100 |
| Connection | The Zendesk connection to use. |
Example Payload for List Article Attachments⤓
List Article Subscriptions
List all subscriptions for an article in the Help Center. | key: listArticleSubscriptions
| Input | Notes | Example |
|---|---|---|
| Article ID | The unique identifier for the article. | 123123213 |
| Locale | The Help Center locale used to populate the article picker. Defaults to 'en-us'. | en-us |
| Pagination | Cursor and page-size controls for paging through results. | |
| Connection | The Zendesk connection to use. |
Example Payload for List Article Subscriptions⤓
List Articles
List all articles in the Help Center. | key: listArticles
| Input | Notes | Example |
|---|---|---|
| Label Names | Restrict results to articles with the specified labels. A maximum of 10 labels can be supplied. See label names for more information. | examplelabel1 |
| Fetch All | When true, automatically fetches all pages of results instead of returning a single page. | false |
| Filters | Optional query controls to sort and refine the results. | |
| Locale | The locale of the articles to retrieve. Defaults to 'en-us'. | en-us |
| Pagination | Cursor and page-size controls for paging through results. | |
| Connection | The Zendesk connection to use. |
Example Payload for List Articles⤓
List Categories
List all categories in the Help Center. | key: listCategories
| Input | Notes | Example |
|---|---|---|
| Fetch All | When true, automatically fetches all pages of results instead of returning a single page. | false |
| Locale | The locale code for the resource. | en-us |
| Page Limit | The number of results to return per page. The maximum is 100; any greater value is capped at 100. | 100 |
| Sort By | The field used to sort the results. | |
| Sort Order | The direction used to order the results. | asc |
| Connection | The Zendesk connection to use. |
Example Payload for List Categories⤓
List Post Subscriptions
List all post subscriptions in the Help Center. | key: listPostSubscriptions
| Input | Notes | Example |
|---|---|---|
| Pagination | Cursor and page-size controls for paging through results. | |
| Post ID | The unique identifier for the post. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for List Post Subscriptions⤓
List Posts
List all posts in the Help Center. | key: listPosts
| Input | Notes | Example |
|---|---|---|
| Fetch All | When true, automatically fetches all pages of results instead of returning a single page. | false |
| Filter By | The field used to filter the results. | |
| Pagination | Cursor and page-size controls for paging through results. | |
| Sort By | The field used to sort the results. | |
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for List Posts⤓
List Section Subscriptions
List all section subscriptions in the Help Center. | key: listSectionSubscriptions
| Input | Notes | Example |
|---|---|---|
| Locale | The Help Center locale used to populate the section picker. Defaults to 'en-us'. | en-us |
| Pagination | Cursor and page-size controls for paging through results. | |
| Section ID | The unique identifier for the section. | 123123213 |
| Connection | The Zendesk connection to use. |
Example Payload for List Section Subscriptions⤓
List Sections
Lists all the sections in the Help Center or in a specific category. | key: listSections
| Input | Notes | Example |
|---|---|---|
| Fetch All | When true, automatically fetches all pages of results instead of returning a single page. | false |
| Filters | Optional query controls to sort and refine the results. | |
| Locale | The locale code for the resource. | en-us |
| Page Limit | The number of results to return per page. The maximum is 100; any greater value is capped at 100. | 100 |
| Connection | The Zendesk connection to use. |
Example Payload for List Sections⤓
List Tickets
List all tickets. | key: listTickets
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for List Tickets⤓
List Tickets Assigned To User
List all of the tickets that have been assigned to a particular user. | key: listTicketsToUser
| Input | Notes | Example |
|---|---|---|
| User ID | The unique identifier for the user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for List Tickets Assigned To User⤓
List Tickets Requested By User
List all of the tickets that a particular user has requested. | key: listTicketsByUser
| Input | Notes | Example |
|---|---|---|
| User ID | The unique identifier for the user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Example Payload for List Tickets Requested By User⤓
List Topic Subscriptions
List all topic subscriptions in the Help Center. | key: listTopicSubscriptions
| Input | Notes | Example |
|---|---|---|
| Pagination | Cursor and page-size controls for paging through results. | |
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for List Topic Subscriptions⤓
List Topics
List all topics in the Help Center. | key: listTopics
| Input | Notes | Example |
|---|---|---|
| Fetch All | When true, automatically fetches all pages of results instead of returning a single page. | false |
| Pagination | Cursor and page-size controls for paging through results. | |
| Connection | The Zendesk connection to use. |
Example Payload for List Topics⤓
List Triggers
List all workflow triggers configured in Zendesk. | key: listTriggers
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for List Triggers⤓
List Users
List all users. | key: listUsers
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. |
Example Payload for List Users⤓
List Webhooks
List all webhooks configured in Zendesk. | key: listWebhooks
| Input | Notes | Example |
|---|---|---|
| Show only instance webhooks | Show only webhooks that point to this instance | true |
| Connection | The Zendesk connection to use. |
Example Payload for List Webhooks⤓
Raw Request
Send a raw HTTP request to Zendesk. | key: rawRequest
| Input | Notes | Example |
|---|---|---|
| Connection | The Zendesk connection to use. | |
| Data | The HTTP body payload to send to the URL. | {"exampleKey": "Example Data"} |
| Debug Request | Enabling this flag will log out the current request. | false |
| File Data | File Data to be sent as a multipart form upload. | [{key: "example.txt", value: "My File Contents"}] |
| File Data File Names | File names to apply to the file data inputs. Keys must match the file data keys above. | |
| Form Data | The Form Data to be sent as a multipart form upload. | [{"key": "Example Key", "value": new Buffer("Hello World")}] |
| Header | A list of headers to send with the request. | User-Agent: curl/7.64.1 |
| Max Retry Count | The maximum number of retries to attempt. Specify 0 for no retries. | 0 |
| Method | The HTTP method to use. | |
| Query Parameter | A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2. | |
| Response Type | The type of data you expect in the response. You can request json, text, or binary data. | json |
| Retry On All Errors | If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors. | false |
| Retry Delay (ms) | The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled. | 0 |
| Timeout | The maximum time that a client will await a response to its request | 2000 |
| URL | Input the path only (/users), The base URL is already included with the configured Zendesk domain (https://YOUR-ZENDESK-DOMAIN.zendesk.com/api/v2). For example, to connect to https://YOUR-ZENDESK-DOMAIN.zendesk.com/api/v2/users, only /users is entered in this field. | /users |
| Use Exponential Backoff | Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored. | false |
The Raw Request action allows interaction with API endpoints that are not covered by other actions.
For example, to list groups, which has an endpoint of /api/v2/groups, enter /groups as the endpoint and select the GET verb.
Example Payload for Raw Request⤓
Search Articles
Search for articles in the Help Center. | key: searchArticles
| Input | Notes | Example |
|---|---|---|
| Brand IDs | Restrict the search to articles or posts within these brands. | 63 |
| Category IDs | Restrict the search to articles or posts within these categories. | 63 |
| Date Range Filters | Optional date filters. Narrow results by exact creation or update date, or by inclusive before and after bounds. | |
| Label Names | The list of label names used to filter the results. | examplelabel1 |
| Locales | The locale to filter the results by. | en-us |
| Filters | Optional query controls to sort and refine the results. | |
| Search Query | The text or search string used to match results. | carrot |
| Connection | The Zendesk connection to use. |
Example Payload for Search Articles⤓
Search Posts
Search posts in the Help Center. | key: searchPosts
| Input | Notes | Example |
|---|---|---|
| Date Range Filters | Optional date filters. Narrow results by exact creation or update date, or by inclusive before and after bounds. | |
| Filters | Optional query controls to sort and refine the results. | |
| Search Query | The text or search string used to match results. | carrot |
| Connection | The Zendesk connection to use. |
Example Payload for Search Posts⤓
Search Users
Return an array of users who meet the search criteria. | key: searchUsers
| Input | Notes | Example |
|---|---|---|
| External ID | The external_id parameter does not support the search syntax. It only accepts ids. | |
| Query | The search query supporting Zendesk search syntax. Accepts a partial or full value of any user property, including name, email address, notes, or phone. Example: query="jdoe". | |
| Connection | The Zendesk connection to use. |
Example Payload for Search Users⤓
Unified Search
Search for knowledge base articles, community posts, and external records in the Help Center. | key: unifiedSearch
| Input | Notes | Example |
|---|---|---|
| Brand IDs | Restrict the search to articles or posts within these brands. | 63 |
| Category IDs | Restrict the search to articles or posts within these categories. | 63 |
| Content Types | Restrict the search to one of these content types: ARTICLE, POST. | |
| External Source IDs | Restrict the search results to the specified external source or sources. | 63 |
| Locales | Restrict the search to articles or posts within these locales. | en-us |
| Pagination | Cursor and page-size controls for paging through results. | |
| Search Query | The text or search string used to match results. | carrot |
| Section IDs | Restrict the search to articles or posts within these sections. | 63 |
| Topic IDs | Restrict the search to posts within these topics. | 63 |
| Connection | The Zendesk connection to use. |
Example Payload for Unified Search⤓
Update Article
Update an existing article's metadata in the Help Center. | key: updateArticle
| Input | Notes | Example |
|---|---|---|
| Body | The main content of the article. | Example Body |
| Article ID | The unique identifier for the article. | 123123213 |
| Title | The headline displayed for the article. | Example Title |
| Assignment IDs | Write-action IDs that associate a record with related entities (sections, authors, permission groups, segments). | |
| Content Tag IDs | The list of content tag IDs to attach to the object. | |
| Display Options | Whether the record is promoted, its ordering position, and whether comments are disabled. | |
| Label Names | The list of label names to attach to the object. | |
| Locale | The locale code for the resource. | en-us |
| Connection | The Zendesk connection to use. |
Example Payload for Update Article⤓
Update Category
Update a category in the Help Center. | key: updateCategory
| Input | Notes | Example |
|---|---|---|
| Category Description | The description of the category to be updated. | Example Description |
| Category ID | The unique identifier for the category. | 12 |
| Category Name | The name of the category to be updated. | Example Category |
| Locale | The locale of the category to be updated. | en-us |
| Position | The position of the category to be updated. | 42 |
| Connection | The Zendesk connection to use. |
Example Payload for Update Category⤓
Update Post
Update a post in the Help Center. | key: updatePost
| Input | Notes | Example |
|---|---|---|
| Content Tag IDs | The list of content tag IDs to attach to the object. | |
| Moderation Flags | Whether the record is featured, pinned, or closed to new comments. | |
| Details | The main body content of the post. | |
| Post ID | The unique identifier for the post. | 12 |
| Status | The current workflow state of the post. | |
| Title | The headline displayed for the post. | Example Title |
| Topic ID | The unique identifier for the topic. | 12 |
| Connection | The Zendesk connection to use. |
Example Payload for Update Post⤓
Update Section
Update a section in the Help Center. | key: updateSection
| Input | Notes | Example |
|---|---|---|
| Category ID | Category ID of the Section to update. | 12 |
| Locale | The locale code for the resource. | en-us |
| Parent Section ID | Parent Section ID of the Section to update. | 12 |
| Position | Position of the Section to update. | 42 |
| Section Description | Description of the Section to update. | Example Description |
| Section ID | The unique identifier for the section. | 123123213 |
| Section Name | Name of the Section to update. | Example Section |
| Connection | The Zendesk connection to use. |
Example Payload for Update Section⤓
Update Ticket
Update a ticket by ID. | key: updateTicket
| Input | Notes | Example |
|---|---|---|
| Assignee Email | The email address of the user assigned to the ticket. | Jane.Doe@example.com |
| Assignee ID | The unique identifier for the user assigned to the ticket. | 403598029853443232 |
| Classification | Priority, status, and type of the record. | |
| File | The file contents to attach to the comment, accepted as either a string or a binary payload. | |
| File Name | The display name to use for the uploaded file. | |
| Requester Organization ID | The unique identifier for the organization the requester belongs to. | 488042375842 |
| Tags | The list of tags to attach to the resource. | Engineering |
| Ticket Comment Body | The plain text description used as the initial comment on the ticket, attributed to the assignee. | This is an example Comment. |
| Ticket Comment HTML Body | The HTML-formatted description used as the initial comment on the ticket, attributed to the assignee. | <p>This is an example Comment.</p> |
| Ticket ID | The unique identifier for the ticket. | 12345 |
| Ticket Subject | The summary line shown at the top of the ticket. | This is an example ticket subject. |
| Connection | The Zendesk connection to use. |
Example Payload for Update Ticket⤓
Update Topic
Update a topic in the Help Center. | key: updateTopic
| Input | Notes | Example |
|---|---|---|
| Manageable By | The user segment allowed to manage the topic. | |
| Position | The position of the topic in the list of topics. | 42 |
| Topic Description | The descriptive text shown below the topic title. | Example Description |
| Topic ID | The unique identifier for the topic. | 12 |
| Topic Name | The display name of the topic. | Example Topic |
| User Segment ID | The user segment ID to associate with the topic. | 15 |
| Connection | The Zendesk connection to use. |
Example Payload for Update Topic⤓
Update User
Update a user by ID. | key: updateUser
| Input | Notes | Example |
|---|---|---|
| Account Settings | Role, moderator permission, and verification state for the record. | |
| Name & Contact Information | Name, email, phone, and other contact channel details. | |
| External ID | A unique identifier from another system. The API treats the ID as case sensitive — for example, "ian1" and "Ian1" are different users. | |
| Organization ID | The unique identifier for the organization. | |
| Profile Details | Alias, notes, and other descriptive attributes for the record. | |
| User ID | The unique identifier for the user. | 488042375842 |
| Connection | The Zendesk connection to use. |
Updating a user's User Role from an end-user to administrator may cause a failed execution. For more information refer to the user permissions guide in the Zendesk docs.
Example Payload for Update User⤓
Changelog
2026-09-25
Expanded the New and Updated Tickets trigger and the Create Webhook event list, corrected several defects in published actions, and restructured action inputs into structured objects:
- Added an optional Look-back Date input to the New and Updated Tickets trigger for performing an initial sync. The initial sync begins on the first recurrence and backfills every ticket created or updated on or after the specified date, seeding each ticket once and ignoring the visibility filters. Leave it empty to start from the first recurrence with no backfill
- Added opt-in batching to the New and Updated Tickets trigger, dispatching changed tickets individually or in configured batches and draining a large backlog within one recurrence instead of one window per recurrence; enabling it changes the shape a downstream step receives
- Added the ticket event types to Events on Create Webhook, which previously offered only the organization and user events, so a webhook can subscribe directly to ticket events
- Fixed Ticket Type and Ticket Priority selections being silently discarded on Create Ticket and Update Ticket
- Fixed List Article Subscriptions returning a not-found error, and the filters on Search Articles and List Articles being ignored
- Fixed list actions with Fetch All enabled returning partial results as if they were complete
- Fixed the New and Updated Tickets trigger returning no tickets on its first recurrence and silently skipping changed tickets on later recurrences, including any ticket changed in the minute before a recurrence ran
- Fixed unset optional inputs reaching Zendesk as empty values rather than being omitted on Create Article, Create Category, Create Section, and Create Post, where an unset Position pinned the new record to the top of its list, an unset Body or Section Description was saved as empty text, and leaving Content Tag IDs empty sent an empty list; also fixed the Article ID, Section ID, and Category ID dropdowns rendering empty on eight actions that carried no Locale, which now offer an optional Locale that populates the dropdown
- Updated the search and list actions to group related inputs: Unified Search, List Articles, List Posts, List Topics, List Article Subscriptions, List Post Subscriptions, List Section Subscriptions, and List Topic Subscriptions group their cursor and page-size inputs into Pagination, with Fetch All, where present, staying a top-level toggle; Search Articles and Search Posts group their date inputs into Date Range Filters and their remaining query controls into Filters; and List Articles and List Sections group their sorting and scoping inputs into Filters
- Updated the user, ticket, article, and post write actions to group related inputs: Create User and Update User into Account Settings and Profile Details, with Update User also grouping its name, email, and phone inputs into Name & Contact Information; Create Ticket and Update Ticket into Classification; Update Article into Assignment IDs and Display Options; and Update Post into Moderation Flags
- Added inline action calling support to 68 actions for improved example output during configuration
- Added output schemas to 68 actions for improved field mapping during configuration
2026-05-26
Added the New and Updated Tickets polling trigger using the Zendesk Incremental Tickets Export cursor stream. The trigger drains pages until end_of_stream and persists both the cursor and the last polled timestamp for accurate created vs. updated partitioning
2026-04-30
Various modernizations and documentation updates
2026-03-16
Improved input field documentation with formatted URL links for better readability
2026-03-13
Enhanced OAuth 2.0 connections with PKCE S256 support for improved authorization security. Removed the Debug Request input from all action inputs.
2026-03-05
Added inline data sources for topic, article, section, and post subscriptions to enable dynamic dropdown selection
2026-02-26
Added inline data sources for users, tickets, topics, and posts to enable dynamic dropdown selection
2025-11-19
Enhanced webhook triggers to support simulated test executions
2025-08-04
Security improvements to the API token connection