Turn Amazon SQS support messages into HubSpot tickets

Every 10 minutes, drain the inbound support queue on Amazon SQS and turn each waiting customer message into a HubSpot ticket.

Call Amazon SQS Receive Message on the designated support-inbox queue URL, using WaitTimeSeconds for long polling and requesting up to 10 messages per pass. For every message that comes back, parse the JSON body to extract the customer email, subject, and message text.

Before opening a ticket, check whether the sender already exists in HubSpot by looking them up by email. If the contact is not already known, call HubSpot Create Contact first with the email and any name you can pull from the payload. Then call HubSpot Create Ticket with a clean drafted subject line, a plain-English summary of what the customer is asking for, the pipeline stage set to New, and an inferred priority: URGENT when the message contains outage or refund language, HIGH when it is a billing question, and MEDIUM for everything else. Associate the ticket with the contact you just found or created.

After the HubSpot ticket has been created successfully, call Amazon SQS Delete Message using the ReceiptHandle from the original message so the same request is never processed twice. If parsing a message fails or the ticket cannot be created, do not delete the message. Leave it in the queue and let the SQS visibility timeout return it for a retry on a later run.

The cron cadence, queue URL, HubSpot ticket pipeline and default owner, and the priority classification rules should all be user-configurable inputs on the workflow.