HeyGen + Apollo.io Integration: Automate Personalized Video in Your Sequences

Architecture Overview

The most common mistake in this integration is treating Apollo as the trigger. Apollo sequences do not natively fire webhooks when a contact enters a sequence. The trigger has to come from your CRM - a HubSpot deal stage change, a Salesforce Opportunity stage, or a manual list enrollment in your CRM.

The correct flow is:

1. CRM event fires (deal stage changes, lead scores, manual trigger)
2. Automation layer fetches contact data from Apollo
3. HeyGen renders a personalized video using that data
4. Automation layer writes the video URL to an Apollo custom field
5. Apollo sequence email step references the custom field variable

Apollo’s job is delivery. It holds the video URL as a contact property and injects it into the email at send time. Everything upstream of that write is handled outside Apollo.

Step 1: Set Up the CRM Trigger

Pick the CRM event that signals intent. A deal moving to “Demo Scheduled” or “Proposal Sent” is typically the right moment - early enough that the video lands before the prospect’s next touchpoint, late enough that they are qualified.

HubSpot: Create a Workflow with enrollment trigger “Deal stage is any of: [your stage]”. Add a “Send a webhook” action pointing at your n8n or Make webhook URL. Include the deal ID, associated contact ID, and contact email in the payload.

Salesforce: Use a Flow with an entry trigger on Opportunity Stage change. Add a Flow Action (HTTP callout) or use a Process Builder webhook step to fire the automation. Pass the Opportunity ID and primary Contact ID.

One important detail: include the Apollo contact ID in your CRM data if you have it stored. If not, you will match by email in the next step, which adds an extra API call and one more point of failure if the email does not match exactly.

Step 2: Pull Personalization Data from Apollo

Add an HTTP Request node calling the Apollo Contacts API to get the data you will pass to HeyGen. You need at minimum: first_name, email, and organization_name.

The response returns the full contact object. Extract contact.first_name, contact.email, and contact.organization_name using a Set node. If you do not have the Apollo contact ID, call the search endpoint instead:

Add a guard after the fetch: if first_name is empty, route to a Slack alert. A missing name produces a video that opens with silence or a broken template variable.

Step 3: Render the HeyGen Video

With the personalization data extracted, call the HeyGen generate endpoint. The request body passes your template ID, avatar ID, voice settings, and the contact variables mapped to your template’s input fields.

Keep “test”: true during development. Test renders are watermarked and free. Switch to false only when the full pipeline is verified end to end.

The response contains data.video_id. Store it in a Set node for the next step.

Then poll for completion. Add a Wait node (90 seconds), then GET /v1/video_status.get?video_id={{video_id}}, then an IF node on data.status: if completed, proceed; if processing, loop back; if failed, route to error handler. Cap at 10 polling iterations.

Step 4: Write the Video URL to Apollo

Once the render completes, data.video_url contains the hosted video link. Write it to a custom field on the Apollo contact using the update endpoint.

First, create the custom field in Apollo: Settings > Custom Fields > New Field. Name it something like personalized_video_url, type URL. Apollo will generate an ID for it.

Add a retry handler on this call. Apollo rate-limits the contacts API and a 429 here means the video URL never lands in Apollo - the sequence email sends with an empty variable. Retry on 429 with a 1-second wait and 3 max attempts.

Error Handling

Two failure modes that will actually happen in production:

Apollo rate limits on contact writes. If you enroll a batch of contacts at once, the PATCH calls will stack up and some will return 429. Add exponential backoff retry on all Apollo write calls. If retries exhaust, log the contact ID and video URL to a separate store (a simple Google Sheet or a Supabase table works) so you can replay the writes without re-rendering.

HeyGen render failures. Renders fail for several reasons: avatar ID changed, voice ID not found, template variable missing. Add an Error Workflow in n8n that posts the failed video_id, contact ID, and error message to Slack. Do not retry render failures blindly - most are configuration errors that retry will not fix.

The 7-Day URL Expiry Problem

HeyGen’s video URLs expire 7 days after render. For same-day outreach this is fine. For multi-step sequences where a follow-up email fires on day 5 or 8, the link will be dead when the prospect clicks.

The fix: immediately after the render completes, download the video file and upload it to a permanent host. S3 or Cloudflare R2 both work. Use the permanent CDN URL in the Apollo write, not the HeyGen URL.

This adds one step to your automation but removes the expiry risk entirely. If you are on a short sequence (same day or next day outreach), skip it. If your sequence has a day 7 or later step that references the video, the re-host is non-negotiable.