Turn Willo accepts into HubSpot contacts and recruiter tasks

Build an agent workflow that closes the loop from Willo to HubSpot when a candidate is accepted.

Trigger: a webhook from Willo on the status_change event. Only run when the new stage is Accept. Ignore Review, Reject, and any other stage — exit early without any HubSpot writes.

When the trigger fires, do this in order:

1) Call Willo Get Participant using the participant key from the webhook payload. Pull the full profile including email, name, phone, the interview title, the AI-generated summary if present, transcripts if present, and the public response URL back to Willo.

2) Call HubSpot Batch Upsert Contacts with the candidate's email as the unique property. Set firstname, lastname, phone, a hs_lead_status or lifecycle stage appropriate for a recruiting pipeline, a source property set to "Willo", and a custom property (default name: willo_interview_title) with the interview title. If the org has not created that custom property yet, still send it — the workflow author should note this in the setup guide so the user creates it or maps it.

3) Call HubSpot Create Note associated with the upserted contact. The note body should contain: the interview title, the AI summary of the candidate's answers (fall back to a short bulleted list of their answers if no AI summary is available), and a link back to the Willo response.

4) Call HubSpot Create Task associated with the same contact. Subject: "Schedule next round with {candidate name}". Body: a one-line reminder plus the link to the Willo response. Due date: 2 business days from now. Owner: the recruiter — accept a recruiter HubSpot owner id as a workflow input so the user can pick who gets the task.

Error handling: if the participant email is missing, log a clear reason and stop — don't create anything in HubSpot. If HubSpot returns a validation error on the custom property, retry the contact upsert without that property so the rest of the flow still succeeds. If Create Note or Create Task fails, still return a useful summary of what did land in HubSpot.

Output: a short summary of the run — candidate name, HubSpot contact id, whether the contact was created or updated, and the ids of the note and task.