Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Zendesk, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands.
All connector references · Connect an account · AI setup and shared results
Browse tickets accessible to the connected Zendesk user.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Zendesk connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. Connect through the provider’s authorization screen. If setup is unavailable, ask your Twidget administrator to configure this connection. |
| Cursor | text | Optional. Continuation value from meta.after_cursor. Omit for the first page. Copy it unchanged and keep the same filters. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Limit | number | Optional. Maximum items requested in this page. Omit for 25; use a whole number from 1 to 100. The provider may return fewer items. |
Result
Returns tickets and cursor metadata when supplied by Zendesk. Put meta.after_cursor into Cursor while meta.has_more is true. links.next is a URL, not the cursor value.
Example
Choose your Zendesk Account and add List tickets. Set Limit = 10. Leave Cursor unset for the first page. These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Reconnect Zendesk if authorization expired. Check ticket permissions and account-specific required-ticket rules. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Read an existing Zendesk support ticket.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Zendesk connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. Connect through the provider’s authorization screen. If setup is unavailable, ask your Twidget administrator to configure this connection. |
| Ticket | text | Required. Numeric ticket ID from List tickets or its Zendesk URL. The connected user needs access to it. Twidget text limit: 8,192 characters; provider-specific limits may be lower. |
Result
Returns the ticket under ticket with id, subject and other accessible fields.
Example
Choose your Zendesk Account and add Get ticket. Set Ticket = "123". These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Reconnect Zendesk if authorization expired. Check ticket permissions and account-specific required-ticket rules. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Create a ticket with a subject and first plain text comment.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Zendesk connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. Connect through the provider’s authorization screen. If setup is unavailable, ask your Twidget administrator to configure this connection. |
| Subject | text | Required. Subject for a new support ticket. Remaining requester/default fields follow Zendesk’s normal account rules. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Comment | text | Required. Plain text initial comment. This command has no attachment or private-comment switch. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
Result
Returns the new ticket under ticket. Remaining defaults follow Zendesk’s account rules.
Example
Choose your Zendesk Account and add Create ticket. Set Subject = "Demo support request"; Comment = "Please review this synthetic request.". These are illustrative values: replace example IDs and addresses with your own permitted test values. An intended live run creates/changes data or sends a message; inspect its receipt before repeating it.
Errors and limits
Reconnect Zendesk if authorization expired. Check ticket permissions and account-specific required-ticket rules. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Isolated tests and live debugging do not call connected providers. Enable Use live data only when you intend to contact the account. Writes, messages and AI requests can change real data or incur provider charges. A successful connection check does not prove access to every action. These examples explain the command contract; they are not evidence of a completed live provider request.
DeepSeek commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → DeepSeek, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All...
Slack commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Slack, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All co...
Together AI commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Together AI, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [...
Notion commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Notion, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All c...
Trello commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Trello, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All c...
