Skip to main content

How to create an EPK in HubSpot | PressKit

Last updated: March 23, 2026 (America/Los_Angeles)

This guide reflects current shipped behavior.

An electronic press kit (EPK) is a public-facing profile page that media outlets, bookers, and PR contacts use when covering or referencing your clients. The challenge: HubSpot stores the underlying data well, but has no native way to publish a structured EPK from a Company record.

PressKit is a CleverCat operational utility for HubSpot: create one EPK per HubSpot Company record with explicit draft/publish controls and a public URL that doesn’t change.

Fast answer

Native HubSpot baseline (manual)

  • Build and host EPK content outside HubSpot (website page builder, PDF, or standalone page).
  • Manually copy relevant fields from HubSpot Company records into the external EPK tool.
  • Send updated links or attachments to media contacts when content changes.

When native is enough

The manual approach is enough when you manage EPKs for a small number of clients, content changes rarely, and media requests are infrequent enough that email-and-PDF handling is acceptable.

Where native breaks

  • Content quickly drifts between CRM records and the published EPK — two separate things that someone has to keep manually aligned.
  • No permanent URL: every version change means updating every place you shared the link.
  • Multiple team members updating different places create version conflicts.
  • No publish-state control: there’s nothing preventing an incomplete or outdated EPK from going live.

Operational utility path

Use PressKit when EPK content changes with release cycles, multiple people need to author or publish, and media contacts need a stable URL they can always share.

Why this is harder than it sounds

  • EPKs sit at the intersection of CRM data, media workflows, and public content. Keeping them aligned manually is an ongoing operations task, not a one-time setup.
  • Booking agents and PR outlets need a URL they can use long-term, not a PDF that’s outdated in three months.
  • Teams creating EPKs for dozens of artist or company clients can’t afford the overhead of rebuilding each EPK from scratch when one field changes.
  • Required content gaps — a missing photo, a missing description — create publishing readiness problems that surface when a journalist is on deadline.

What you’ll get (PressKit)

  • Create one EPK profile per HubSpot Company record from Company context in HubSpot.
  • PressKit Editor opens from the Company record’s workflow actions.
  • Required fields before publish (default mode): Artist Name and Description — prevents empty EPK pages from going live.
  • Supported media: image uploads, document uploads, and HTTPS video links.
  • Public route contract: /epk/:portalId/:publicId — the URL stays consistent across all future content updates.
  • Draft state: EPKs are private until explicitly published.

Prerequisites

  • PressKit installed in your HubSpot portal.
  • One or more HubSpot Company records representing the entities you’re creating EPKs for.
  • A test Company for first-run validation.
  • Decision on portal visibility posture: default mode (draft-first) or auto-publish-by-default.

Boundaries and limitations

Does

  • Create structured EPK profiles from HubSpot Company context.
  • Keep authoring, draft/publish state, and public URL under explicit control.
  • Provide a consistent public URL per Company profile.

Does not

  • Support EPK profiles for contacts, deals, or other non-Company HubSpot objects.
  • Provide password-protected EPK links.
  • Replace full media asset management or press release distribution.
  • Deep-link to HubSpot’s native CMS or website pages.

Validation slice checklist (before rollout)

  • Open the PressKit Editor from one test Company record.
  • Add the required fields (Artist Name, Description) and save as draft.
  • Confirm the public URL is not accessible while in draft.
  • Publish the EPK and verify the /epk/:portalId/:publicId URL renders correctly.
  • Add an image, a document, and a video link; confirm all render on the public page.
  • Update a field in the Editor and confirm the public page reflects the change without the URL changing.
  • Review Portal Settings before enabling auto-publish-by-default.

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID and Company ID/URL.
  • Profile status (draft/published) and the publicId/share URL.
  • Steps to reproduce and screenshots of the PressKit Editor and the public page.
  • Media details (file type, size) or HTTPS video URL used.
  • Any error message or request ID shown.

Fallback: use Known limitations and Support with portal context.

Next steps

FAQ

Can I create EPKs for contacts, not just companies?

No. PressKit is built around HubSpot Company records. One EPK profile per Company.

Does PressKit host the EPK page, or do I need my own server?

PressKit hosts the public EPK page at /epk/:portalId/:publicId. No external hosting required.

What’s the public URL format?

Published EPK pages render at /epk/:portalId/:publicId. The URL stays the same across all future content updates.

Can I add video to an EPK?

Yes. PressKit supports image uploads, document uploads, and HTTPS video links.

Can multiple team members edit the same Company’s EPK?

Yes. The PressKit Editor opens from HubSpot Company context, accessible to users with the appropriate HubSpot permissions.

HubSpot does a lot. Why add PressKit for EPKs?

HubSpot does a lot. For everything else — structured EPK creation from HubSpot Company records with a permanent public URL — there’s CleverCat.