Auto-attach podcast appearances to new HubSpot contacts

Build a code workflow that enriches every newly created HubSpot contact with a summary of their public podcast appearances from Podchaser.

Trigger: a HubSpot webhook on the contact.creation event. The workflow should fire once per new contact.

Inputs from the trigger payload: the new contact's HubSpot ID, full name (firstname + lastname), and company name if present.

Pipeline (deterministic, no LLM judgment in the middle):

1. Call Podchaser Search Credits with the contact's full name to find every podcast credit attributed to them. If a company is present on the contact, you can use it as a tiebreaker when more than one creator matches the name, but do not require a company match.

2. Take the top 10 most recent credits (sort by episode air date or credit date, descending).

3. For each of those 10 credits, call Podchaser Get Podcast by Identifier to fetch the show title and the show URL. Cache by podcast ID inside the run so we never fetch the same show twice.

4. Format a single compact note. Header line: "Podchaser podcast appearances (top 10 most recent)." Then one bullet per credit with: show name, role (host / guest / producer / etc.), episode title, episode date in YYYY-MM-DD, and the show URL as a clickable link. Keep the note under HubSpot's note size limits; if a field is missing, omit it gracefully.

5. Call HubSpot Create Note with the formatted body and associate it to the new contact's ID so the note shows up directly on that contact's timeline.

Empty-result handling: if Podchaser Search Credits returns zero results for the name, still call HubSpot Create Note with a short body that reads "No public podcast appearances found on Podchaser as of {today's date in YYYY-MM-DD}." so reps can see the lookup ran rather than wondering whether it was skipped.

Error handling: if Podchaser is unreachable or returns an auth error, retry once with backoff, then fall back to writing a note that reads "Podchaser lookup failed at {timestamp}; retry later." Never block contact creation. If HubSpot Create Note itself fails, log the error and stop. The workflow should be idempotent if the same webhook is delivered twice (use the contact ID + the day's date as a dedupe key for the note).

Out of scope for this workflow: ranking, scoring, or summarizing the appearances; emailing the rep; updating any contact properties beyond the attached note. Keep it tight: webhook in, single note out.