Text new Typeform leads instantly from your Linq iMessage number

Build an agent workflow that wins the first five minutes on every new inbound lead by replying with a personalized iMessage from my Linq number, while keeping HubSpot perfectly up to date.

Trigger: an outgoing webhook from Typeform on each new form submission. The Typeform payload includes the form_response object with the answers array, hidden fields, and definition. Parse it to extract the lead's name, email, phone number, company, and the qualifying answers (typical fields: budget, timeline, use case, team size, current tool).

Step 1. Classify fit and urgency. Read the qualifying answers and label the lead as hot, warm, or cold. Hot means strong budget plus a near-term timeline plus a clear use case. Warm means two of those three. Cold means none of the above or a clearly out-of-scope answer. The exact thresholds should live near the top of the instructions so I can tweak them.

Step 2. For hot and warm leads only, send a personalized iMessage. First, call Check iMessage Capability on Linq for the lead's phone number. If the phone field is empty, malformed, or the capability check says iMessage is not available, skip the text entirely and move on to the HubSpot steps. If iMessage is available, draft a short opener (two short sentences, no emoji, no exclamation marks, no em dashes) that references one specific thing the lead wrote in the form, like "saw you're trying to ship {X} by {date}" or "noticed your team is on {tool} today." Then call Create Chat on Linq from my Linq sender number to the lead's phone, with the opener as the initial message. Use the Linq number from my account (look it up if needed, do not hardcode).

Step 3. In parallel with the text (do not block on it), upsert the lead into HubSpot. Use Batch Upsert Contacts with email as the unique identifier. Fill in firstname, lastname, phone, company, lifecyclestage of lead, and a source property set to typeform. Map each qualifying answer to a contact property (budget, timeline, use case, team size, current tool, anything else the form collected). If a property does not yet exist on the contact object, fall back to writing it into the note instead of failing.

Step 4. Create a HubSpot note with Create Note, associated with the contact from step 3. The note body should contain the full set of Typeform answers, the classification (hot, warm, or cold), and whether the iMessage was sent, skipped because no phone, or skipped because iMessage was unavailable. This gives the AE a single source of truth when they open the contact.

Step 5. For cold leads, do the HubSpot upsert and note but skip the iMessage entirely. Cold leads still belong in the CRM, they just do not deserve white-glove speed-to-lead.

Guardrails: never text the same phone number twice in a row from the same submission, never send if the lead opted out of marketing on the form, and if any Linq call fails, log the error to the HubSpot note and keep going with the rest of the steps so the CRM record always lands.