Route HubSpot MQLs into the right GetResponse nurture campaign

Build me an agent that routes newly qualified HubSpot leads into the correct GetResponse nurture campaign the moment they become sales-ready, and posts a handoff summary to Slack.

Trigger: a HubSpot webhook that fires whenever a contact's lifecycle_stage property changes to marketingqualifiedlead or salesqualifiedlead. The webhook payload includes the contactId and the new lifecycle stage.

When the webhook fires, do the following:

1. Call HubSpot Get Contact with the contactId from the payload and pull the properties I use to pick a campaign: email, firstname, lastname, jobtitle, company, industry, numberofemployees, hs_lead_source, hs_analytics_source, hubspot_owner_id, lifecyclestage, and any recent activity fields. If Get Contact does not surface enough context, use HubSpot Search Contacts to look the record up by email.

2. Call GetResponse List Contacts filtered by the lead's email to check whether they are already subscribed and which GetResponse campaign they are currently in.

3. Decide which GetResponse campaign is the best fit based on the HubSpot profile. Route by industry first, then by company size, then by lead source. I will maintain the list of GetResponse campaigns and the routing rules in a config section at the top of the workflow. Pick a sensible default campaign if nothing matches.

4. If the lead is NOT already in GetResponse, call GetResponse Create Contact to add them to the chosen campaign. Attach two tags: mql-from-hubspot (or sql-from-hubspot depending on the lifecycle stage) and an industry tag such as industry-saas. If a required tag does not exist yet in GetResponse, call GetResponse Create Tag first to create it.

5. If the lead IS already in GetResponse, call GetResponse Update Contact to add the qualification tag and industry tag to their existing subscription. Do not move them between campaigns unless the current campaign is clearly wrong for their new profile.

6. Call Slack Send a Message to post a short handoff to a channel I configure (default: #sales-handoffs). The message should include the lead's name and company, their new lifecycle stage, the GetResponse campaign they were routed to, the tags applied, a one-sentence reason for the routing decision, and a direct link back to the HubSpot contact record. Mention the HubSpot owner by name so they see it.

Handle these edge cases: if the HubSpot contact has no email address, skip GetResponse entirely and post a Slack warning that the lead cannot be nurtured. If the GetResponse Create Contact call returns a duplicate error, fall back to Update Contact. If any step fails, still post a Slack message so the handoff never goes silent.

The goal is to close the very common gap where MQLs sit in the CRM without ever getting a nurture email. Keep the routing logic easy to edit and keep the Slack summary short and scannable.