Skip to main content

​
Overview

The HubSpot integration gives marketing teams one conversational interface for HubSpot email operations. Hand Grady an approved campaign brief and it can create a branded HubSpot marketing email, apply the edits you describe, and surface a rendered preview for review — while HubSpot continues to operate underneath as the connected system of record.
The HubSpot integration must be enabled for your organization by the Gradial team, and a HubSpot portal must be connected through OAuth. Contact your Gradial team for access and setup guidance.

​
Why use Gradial with HubSpot

Building a campaign email normally means translating a brief across several applications by hand — copying headlines into a template, hunting down the right approved layout, swapping images, checking every link. The HubSpot integration collapses that into a single conversation:
  • The brief becomes the input — describe or attach the approved brief instead of retyping it into an editor
  • Approved structure is preserved — start from an existing branded email rather than rebuilding styling and sender configuration
  • Review happens in the thread — open a rendered preview without leaving Gradial
  • Publishing stays deliberate — sending is always a separate, human-approved action

​
What Grady can do

​
Turn a campaign brief into an email draft

Give Grady an approved campaign brief and it creates a new HubSpot marketing email from it — no manual translation of the brief across multiple tools.

​
Reuse a branded template

Grady can clone an existing HubSpot email so the new draft inherits approved structure, styling, sender configuration, and branding.
Cloning does not copy recipient lists. If the new email needs an audience, prepare one explicitly — see Audience support below.

​
Edit a designed email

Grady can update supported modules in a designed email and verify that each requested change was actually applied:

​
Produce a reviewable artifact

Grady publishes a rendered email preview directly in the thread so you can review the result without switching tools. When the preview can’t fully represent the final email, Grady flags it clearly so you know to complete exact review in HubSpot.

​
Audience support

When your workflow includes audience preparation, Grady can find an existing HubSpot contact list or create a new one and attach it to the email.

​
Publishing

Publishing is a real send. It remains a separate action that requires explicit human approval and is validated against the final email content before it goes out.
Publishing sends the email. Grady will not publish without explicit human approval, and publishing depends on the connected portal’s HubSpot permissions and portal eligibility.

​
Example prompt

​
Setup and permissions

1

Enable the integration

Contact your Gradial team to enable the HubSpot integration for your organization. This gates HubSpot setup, OAuth, and Grady’s HubSpot capabilities.
2

Connect your HubSpot portal

A Gradial organization admin connects the HubSpot portal to Gradial through OAuth.
3

Grant the right HubSpot scopes

What Grady can do is bounded by the OAuth permissions the connected portal grants:
  • Email drafting requires HubSpot content access
  • Image replacement requires files access
  • Audience preparation requires CRM Lists access
  • Publishing additionally requires an eligible HubSpot portal and the appropriate HubSpot permission
4

Run the workflow

Once connected, authorized workspace users can run the Grady email workflow. All HubSpot operations remain limited by the connected portal’s granted permissions.

​
Current limitations

  • Designed-email editing is module-scoped. Only supported text, button, image, and image-link modules can be edited.
  • The Gradial artifact is a simplified review surface. Incomplete previews require exact final review in HubSpot.
  • Cloning does not copy recipient lists.
  • No test sends. HubSpot does not expose a public marketing-email test-send API, so Grady cannot trigger one.
  • Publishing is a real send and always requires explicit human approval.

​
Not in this release

This release covers HubSpot email operations with optional audience support. Contacts, companies, deals, pipelines, associations, engagement summaries, forms, campaign import, owners, and standalone file-management workflows are out of scope.