Log Hume EVI voice calls to HubSpot every morning

Build an agent workflow that syncs my Hume EVI voice qualification calls into HubSpot every weekday morning.

Trigger: cron. Run every weekday (Monday through Friday) at 7:00am in my local timezone. Hume is not a poll provider, so this must be a scheduled cron trigger, not a poll trigger.

On each run, the agent should:

1. Use Hume's "List Chats" operation to fetch EVI chats that ended in the last 24 hours. Page through results if needed and only keep chats whose end time falls inside that window.

2. For each chat, call Hume's "List Chat Events" operation to pull the full transcript, including the emotion features returned on user messages. Use the events to understand what the caller said, what the assistant said, and how the caller's emotional signals shifted during the conversation.

3. Write a concise call summary (roughly 4-8 sentences) that covers: what the caller was asking about, the sentiment arc you can see in the Hume emotion features (for example "started frustrated, ended interested"), any objections or questions raised, and the concrete next step. The emotion signals are Hume's differentiator versus a plain transcript, so make sure the summary explicitly references them.

4. Pull the caller's phone number and email from the chat metadata (Hume exposes these on the chat and its events when the EVI config collects them). Use HubSpot's "Search Contacts" operation to find a matching contact, searching by phone first and falling back to email. Treat a match as a single unambiguous contact; if multiple contacts match, use the most recently updated one and note that in the summary.

5. When a contact is matched, use HubSpot's "Create Note" operation to attach the call summary as a note on that contact. Include the chat's start time, approximate duration, and a link back to the Hume chat in the note body so it's easy to jump to the raw transcript. Associate the note with the contact via the associations field.

6. When no HubSpot contact matches the phone number or email (or when the chat had no phone or email at all), skip the HubSpot write. Instead, use Slack Bot's "Send a Message" operation to post to a dedicated channel (let me pick the channel during setup, default suggestion: #hume-unmatched-calls). The Slack message should include the caller's phone/email if known, the chat's start time, and a one-line summary so I can decide whether to create a new HubSpot contact by hand.

Other behavior:

- If a chat has already been written to HubSpot on a previous run (for example if I rerun the workflow manually), don't create a duplicate note. The simplest heuristic is to check the contact's recent notes for one whose body already references the Hume chat id.

- If "List Chats" returns nothing for the last 24 hours, exit quietly without posting anything to Slack.

- Log a brief run summary at the end: how many chats were processed, how many were written to HubSpot, and how many were posted to Slack as unmatched.