Carbon Copy
CC and BCC for HubSpot transactional emails.
HubSpot's native Single-Send Email workflow action takes a single recipient: the enrolled object. There is no native way to add CC or BCC recipients to a transactional email from a workflow. Carbon Copy fixes that one missing field.
One recipient is not how transactional email actually works.
Real transactional emails get CC'd to a manager, BCC'd to an archive, and routed through a reply-to that points at the team inbox, not the sender's personal address. HubSpot's Single-Send Email workflow action exposes none of that: one recipient, no CC, no BCC, no reply-to override. Teams either drop the workflow and send manually, or build a custom code action that re-implements the transactional API.
A workflow action that adds the missing envelope fields.
Carbon Copy is a workflow action you drop into any HubSpot workflow on Contact, Company, Deal, or Ticket. It takes a Single-Send template ID, an optional CC list, an optional BCC list, and an optional reply-to override. CC and BCC accept semicolon-separated email lists with HubSpot personalization tokens. The action calls the Single-Send API directly and surfaces the send status as a workflow output so downstream branches can react to success or failure.
Built and deployed. Marketplace listing in progress.
The action is in production on Vercel and signs every webhook with HubSpot's v3 signature scheme. The HubSpot marketplace listing is being filled out (support contact, screenshots, billing terms). Carbon Copy requires the HubSpot Transactional Email add-on or Marketing Hub Enterprise; the action probes the portal's granted scopes during token refresh and fails cleanly if the add-on is not active.
Tell me when Carbon Copy hits the marketplace.
One email when the listing goes live and Carbon Copy is installable from inside HubSpot.