Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Freshdesk, 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 a page of recent Freshdesk tickets.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Freshdesk 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. |
| Page | number | Optional. Page number. Omit to start at 1; increase by 1 to continue, keeping other selection fields unchanged. Allowed whole numbers: 1 to 300. |
| 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 a list of ticket objects. The provider’s normal recent-ticket period applies, typically tickets created in the last 30 days, not an all-history export. Page starts at 1 and can reach 300; no date filter is exposed.
Example
Choose your Freshdesk Account and add List tickets. Set Page = 1; Limit = 10. These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Check saved subdomain/API key, agent ticket permissions and required ticket rules. List tickets exposes the provider’s recent-ticket view, not all history. 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 a Freshdesk support ticket by numeric ID.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Freshdesk 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. |
| Ticket | text | Required. Numeric ticket ID from List tickets or its Freshdesk URL, in the connected account. Twidget text limit: 8,192 characters; provider-specific limits may be lower. |
Result
Returns the ticket object with id, subject, status, priority and other accessible fields.
Example
Choose your Freshdesk 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
Check saved subdomain/API key, agent ticket permissions and required ticket rules. List tickets exposes the provider’s recent-ticket view, not all history. 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 Freshdesk ticket for a requester email.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Freshdesk 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. |
| text | Required. Requester email for a new ticket. Freshdesk may create the requester contact if needed. Twidget text limit: 32,768 characters; provider-specific limits may be lower. | |
| Subject | text | Required. Subject of a new ticket. The command requests Open status and Low priority. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Description | text | Required. Initial ticket description. Simple text is sufficient; Freshdesk also supports its normal HTML description format. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
Result
Returns the created ticket object. The command requests status 2 (Open) and priority 1 (Low); account-specific rules may require additional setup.
Example
Choose your Freshdesk Account and add Create ticket. Set Email = "alex@example.test"; Subject = "Demo support request"; Description = "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
Check saved subdomain/API key, agent ticket permissions and required ticket rules. List tickets exposes the provider’s recent-ticket view, not all history. 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.
Cohere commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Cohere, 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...
Todoist commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Todoist, 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 ...
GitHub commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → GitHub, 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...
Linear commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Linear, 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...
Cloudflare commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Cloudflare, 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. [A...
