Auto-enrich new Flodesk subscribers and sync to HubSpot

Build me an agent workflow that fires on a Flodesk webhook every time a new subscriber is created. The trigger is Flodesk's subscriber.created event. The payload includes the subscriber's id, email, first_name, last_name, status, and any custom_fields they submitted.

For each new subscriber, the agent should do quick web research using the email domain plus whatever name and custom field data Flodesk captured. The goal is to figure out who this person likely is across three buckets: a personal or freelance email (Gmail, Outlook, Yahoo, ProtonMail, or a sole-proprietor domain), a small business owner (small or mid-sized company domain), or someone at a larger company (recognizable mid-market or enterprise domain). It should also try to determine a rough industry when it can tell.

Based on that classification, call Flodesk's Create or Update Subscriber operation to write back a short one-line bio and a category value into the subscriber's existing custom fields. The category value should be one of: solo_and_creator, small_business, or larger_team. The one-line bio should be plain text, no more than about 140 characters, summarizing who this person likely is and what they likely do.

Then call Flodesk's Add Subscriber to Segments operation to drop the subscriber into the matching segment. The user will configure three segment IDs at build time: one for Solo and Creator, one for Small Business, and one for Larger Team. Also configure a default Newsletter segment ID as a fallback. Match the category to the matching segment ID.

Finally call HubSpot's Create Contact operation so the same person lands in the CRM. Pass email, firstname, lastname, lifecyclestage set to subscriber, and when the research returned a confident answer, also pass the company name and industry.

Important fallback behavior: if the research returns nothing confident, do not guess. Skip writing the bio and category to Flodesk, skip the company and industry on the HubSpot contact, drop the subscriber into the default Newsletter segment, and still create the bare HubSpot contact with just email, name, and the subscriber lifecycle stage. Better to route them safely than to mislabel them.

At build time, ask me for the four Flodesk segment IDs (Solo and Creator, Small Business, Larger Team, default Newsletter), the names of the Flodesk custom fields to write the bio and category into, and whether to overwrite existing values on subscribers who already have those fields filled in.

Additional information

What does this prompt do?

Listens for every new Flodesk subscriber the moment they sign up, no matter where they came from.
Researches the email domain and any name or custom field data to figure out if they are a personal or freelance email, a small business owner, or someone at a larger company, plus a rough industry where possible.
Writes a short one-line bio and a category value back to the subscriber in Flodesk and drops them into the matching segment, like Solo and Creator, Small Business, or Larger Team.
Creates a matching contact in HubSpot with email, name, lifecycle stage of subscriber, and the enriched company and industry, so the same person shows up in your CRM from the very first email.

What do I need to use this?

A Flodesk account with API access and segments set up for the audience types you want to route into (for example Solo and Creator, Small Business, Larger Team, and a default Newsletter segment).
Custom fields on your Flodesk subscribers to hold the short bio and the category value the agent will write.
A HubSpot account where new contacts can be created, with permission to set lifecycle stage, company, and industry on contact records.

How can I customize it?

Rename the segment buckets to match how you actually think about your audience. You might use Creator, Agency, and Enterprise instead of Solo, Small Business, and Larger Team.
Change which fields the agent writes back, for example send the enriched industry into a different Flodesk custom field or skip the one-line bio entirely.
Adjust how the HubSpot contact is created, for example use a different lifecycle stage, add a lead source value, or assign the contact to a specific owner.

Frequently asked questions

Does this work for subscribers who sign up from any form, not just one specific source?

Yes. It reacts to Flodesk's subscriber created event, which fires for every new subscriber regardless of which form, landing page, or import they came in through.

What happens if the research cannot confidently identify the subscriber?

The agent skips the enrichment fields rather than guess. The subscriber still gets dropped into a default Newsletter segment and still creates a bare contact in HubSpot so nothing falls through the cracks.

Can I use this if I do not have HubSpot?

Yes. You can ask the agent to drop the HubSpot step and only do the Flodesk enrichment and segmenting, or swap HubSpot for a different CRM during the build.

Will it overwrite data on existing subscribers?

It uses Flodesk's create or update subscriber action, so it updates the same person rather than creating duplicates. You can tell the agent to only fill empty fields if you do not want it touching existing values.

How accurate is the audience classification?

Domain-based research is a strong signal but not perfect. The agent is told to skip the category and bio fields when it is not confident, so wrong guesses are rare. You can also review and adjust the segments inside Flodesk at any time.