Triage every inbound SimpleTexting message in Slack and HubSpot

Build me an agent workflow that triages every inbound text message my SimpleTexting number receives. A human still sends the final reply, the agent only researches, classifies, logs, and drafts.

Trigger: a webhook fired by SimpleTexting whenever a new incoming message arrives. SimpleTexting posts the inbound payload to a webhook URL I configure via its API and Webhooks settings, so this workflow should expose an incoming webhook that SimpleTexting can call. The payload includes the sender phone number, the message body, and the SimpleTexting contact info.

For each inbound message the agent should:

1. Look up the sender's phone number in HubSpot using HubSpot Get Contact (search by phone). If no contact is found, call HubSpot Create Contact to create one using the phone number and any name fields SimpleTexting passes through, so every conversation is tied to a CRM record.

2. Classify the message into exactly one of: sales lead, support question, opt-out or complaint, FAQ, or spam. Use the message body plus any HubSpot context (lifecycle stage, recent notes, deal history) to make the call.

3. Draft a short suggested reply, two to four sentences max, written in a friendly professional tone. If the classification is opt-out or spam, the draft should acknowledge the opt-out or recommend no response. Do not send this reply anywhere. It is for a human to copy.

4. Log the inbound text on the HubSpot contact using HubSpot Create Note. The note should contain the full message body, the classification, and the drafted reply, and it should be associated with the contact record from step 1.

5. Post a structured alert to a Slack triage channel using Slack Send a Message. The Slack message must include: sender name (or phone if name is unknown), classification with an emoji prefix that matches the category, the full inbound message body in a quote block, a clickable link to the HubSpot contact record, and the drafted reply in a code or quote block so it is easy to copy. End the message with a short instruction that whoever takes it should send the reply from SimpleTexting if they approve.

Do not auto-reply via SimpleTexting Send Message. The Send Message operation exists for the human teammate to use manually from the SimpleTexting UI. The agent must stay read-only on the outbound SMS side.

Inputs to expose as workflow configuration: the Slack channel ID for triage alerts, an optional HubSpot owner ID to assign newly created contacts to, and an optional map from classification to Slack channel for teams that want sales leads, support, and complaints routed to different channels.