Contents
- Introduction
- Scenario Builder Application
- Scenario Blocks
- Accept
- Add to Calling List
- Answer
- Attached Data
- Collect Digits
- Comment
- Connect Call
- Connect Chat
- DB Execute
- Exception Handler
- Exit
- Fetch URL
- Find Agent
- Get Next Record
- Get Statistics
- Get User Configuration
- Goto
- If
- Internal Message
- Log
- Menu
- Play Prompt
- Record
- Request Callback
- Request Input
- Request Skill or Service
- RightNow Create Object
- RightNow Screen Pop
- RightNow Search
- RightNow Select Account
- RightNow Update
- Salesforce.com Delete
- Salesforce.com Insert
- Salesforce.com Screenpop
- Salesforce.com Search
- Salesforce.com Update
- Save Survey Response
- Self-Service Provided
- Search Directory
- Send Message
- Set Agent State
- Set Disposition
- Set Priority
- Set Prompt Language
- Set Variable
- Start Another Scenario
- Stop Prompt
- Voicemail
- Wait
- Web Screen Pop
- 1 Zendesk Create Object
- Zendesk Screen Pop
- Zendesk Search
- Zendesk Select Account
- Zendesk Update
- Variables and Expressions
- Voice Segment Types
- Scenario Example
Zendesk Create Object
This block creates a specified object in the Zendesk database. Object that can be created are tickets and users. For more information see the following articles:
https://developer.zendesk.com/rest_api/docs/core/tickets#creating-tickets
https://developer.zendesk.com/rest_api/docs/core/users#create-user
Note that to populate the custom fields in Zendesk activity history records, the Attached Data block shall be used.
Conditional Exits
- Failed – Executes if the create operation failed.
Settings
- Title text - The name of the block instance.
- Object type – Type of the Zendesk object to be created. Can be either a ticket or a user.
- Variable name of object ID – Name of the variable that will be used as identifier for the Zendesk object to be created. Will be set only if the block succeeds.
- Set fields – Reserved.
- Raw JSON – Object properties specified in JSON format (see the links above).
The code and the body of the received HTTP response will be stored in local variables $(integrationResultCode) and $(integrationResultBody) respectively. For troubleshooting purposes, use EMail or Internal Message block to obtain content of responses indicating a failed attempt to create an object. For more information, see description of variable $(integrationResultBody).