New ticket
Start the Workflow when new ticket occurs.
Workflow template
Send ticket IDs and creation times to a support processing queue. Consumers can retrieve the ticket through Zendesk without storing the customer message in SQS. Choose a standard SQS queue at installation. Consumers should handle duplicate deliveries.
How it works
Start the Workflow when new ticket occurs.
Delivers a message to the specified queue. A message can include only XML, JSON, and unformatted text. The following Unicode characters are allowed. For more information, see the W3C specification for characters. #x9 | #xA | #xD | #x20 to #xD7FF | #xE000 to #xFFFD | #x10000 to #x10FFFF If a message contains characters outside the allowed set, Amazon SQS rejects the message and returns an InvalidMessageContents error. Ensure that your message body includes only valid characters to avoid this exception.
Before activation
Open the template in FastHook to create an editable Workflow Draft.
Connect your accounts for Zendesk, Amazon SQS.
Review the Steps, field mappings, routes, and provider settings.
Activate the Workflow when the Draft is ready, then verify a test run.
No. FastHook creates a disconnected Draft. Connect your own Zendesk, Amazon SQS accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.