Swayam

It would be great if you share how much time you have, and a bit about the video specifications. Thanks

Pat, what would you personally recommend if someone wanted something more robust?

I think your budget constraints matter too. Your options increases. A few people have built solid content workflows with Claude + n8n/Zapier, especially around research → drafting → repurposing → publishing pipelines. One thing I’d recommend before going deep into agents is designing the “content system” first:

The workflows usually become way more reliable when the AI is only responsible for specific steps instead of “create everything autonomously.” Some genuinely useful resources:

A pattern I keep seeing work well: Research agent → outline agent → drafting agent → formatting/repurposing → human review → scheduler/posting Also, if you’re using Claude Code specifically, it becomes really powerful when paired with structured file systems + markdown knowledge bases instead of trying to keep everything inside prompts. Hope that helps

Koalify is quite good, used it quite a lot, few friends of mine had recommended it, it's great.

Fair enough, Pat I think I threw around “complexity” too loosely there. What I really meant is: I’ve seen this go sideways when the event format changes every quarter and marketing ops is already underwater. In those cases, keeping the event layer outside has saved the team from becoming the bottleneck. But you’re absolutely right, if the structure is stable and there’s someone who can own the object properly, it’s a much cleaner reporting path. Appreciate you keeping me honest here.

Haha true Pat, the object exists either way 😄 But the pain doesn't have to. A custom object in HubSpot means schema dependencies, admin bottlenecks, and a structure that fights back every time the use case evolves. A custom app I was talking about adapts to your new event, new field, new report without touching HubSpot's architecture at all. Same data, zero additional friction inside the CRM, and it's EASY TO USE ;)

Hi Paris The reason every option you're considering feels like a workaround is because it is — HubSpot's contact/company model wasn't built for event-instance tracking. You're not missing something obvious, it genuinely doesn't have a clean native answer. This is something I have seen some colleagues facing and I have helped them using a rather simpler way: track the event layer completely outside HubSpot, sync only the summary back as a contact property. Your reps get their reporting, your HubSpot stays clean, and you don't add a fourth custom object. Hope that helps. Would love to discuss further!