Rockkt for HubSpot

Rockkt Gifts & Letters: setup guide

Rockkt prints and posts personal letters, with or without a gift, for your sales team. The HubSpot app lets a HubSpot workflow start a Rockkt send for a contact or a deal, and writes what happens next back onto that contact and deal, so you can build your own workflows on it.

Who it is for

How to connect

  1. In Rockkt, a Client Admin opens Integrations (in the menu) and presses Connect HubSpot.
  2. HubSpot asks a HubSpot Super Admin to approve the app. Only a Super Admin can install it.
  3. Back in Rockkt, finish in the same browser, signed in as the person who pressed Connect.
  4. Rockkt matches your HubSpot owners to Rockkt users by email. Match anyone else by hand, and press Refresh owners after adding people.

One HubSpot account connects to one Rockkt company at a time. A demo workspace cannot connect.

Your settings in Rockkt

A task when a recipient shows interest

When someone presses “I'm interested” on a send's landing page, or watches its video for the first time, Rockkt creates a HubSpot task: “Call <first name> today”, high priority, due today, linked to the contact and to the deal when the send came from one, with the order reference and a link to the send in Rockkt. It goes to the contact's owner, or, when the contact has no owner, to the HubSpot owner matched to the Rockkt sender; with neither, no task is made. One task per person per send: a second signal on the same send is added to that task as a note. A landing page view alone never makes a task.

It covers sends started from HubSpot, and other sends whose recipient Rockkt can match to a HubSpot contact (saved with Save to HubSpot, or the one contact with the recipient's email). It is on once you connect; a Client Admin can turn it off in Rockkt, on the Integrations page, under HubSpot. It needs no extra HubSpot permission.

Save to HubSpot from Rockkt One

Rockkt One is Rockkt's side panel for LinkedIn. With this setting on, a rep on a LinkedIn profile can press Save to HubSpot to save that person, and their company, to your HubSpot. One person per press, never in bulk. It is off until a Client Admin turns it on in Rockkt, on the Integrations page, under HubSpot: Update existing contacts only, or Create and update.

A connection made before this feature needs reconnecting once, to allow companies. Until then Rockkt One shows nothing about it.

The workflow step “Send a Rockkt playbook”

Add it to a contact or deal workflow. On a deal, the recipient is the deal's primary contact, or its first contact when none is primary. The sender is the record's HubSpot owner.

The step gives your workflow Rockkt result, Rockkt reason, Rockkt order reference, Rockkt confirm link and Rockkt message. Branch on the result, or copy the confirm link into an email from your own HubSpot.

The Rockkt card on contact and deal records

The app adds a card called “Rockkt” that can sit on contact and deal records. To add it, a HubSpot Super Admin, or anyone allowed to customize record page layouts, opens a contact record, chooses Customize record, adds the Rockkt card to a tab in the middle column, and saves. Do the same on a deal record.

Drafts and approvals

A draft waits in the rep's Outbox in Rockkt (and in Rockkt One). Nothing is sent or charged until the rep opens it, checks it and presses Send. Drafts do not count towards the monthly limit.

A send waiting for approval shows in Rockkt on the Integrations page, under HubSpot, where any Client Admin can approve or decline it.

What Rockkt writes back to HubSpot

Rockkt adds a “Rockkt” property group to your contacts and deals, and fills it in three ways:

PropertyInternal nameOnWhat it holds
Rockkt gift statusrockkt_gift_statusContacts and dealsWhere the latest Rockkt send is.
Rockkt last orderrockkt_last_order_refContacts and dealsThe reference of the latest Rockkt send.
Rockkt last playbookrockkt_last_playbookContacts and dealsThe Rockkt playbook the latest send used.
Rockkt confirm linkrockkt_confirm_linkContacts and dealsThe link the recipient uses to confirm or give their address, while Rockkt is waiting for them.
Rockkt landing pagerockkt_landing_page_urlContacts and dealsThe landing page that goes with the latest Rockkt send.
Rockkt landing page viewedrockkt_landing_page_viewed_atContacts and dealsWhen the recipient first opened the landing page.
Rockkt interestedrockkt_interested_atContacts and dealsWhen the recipient first pressed "I'm interested" on the landing page.
Rockkt video watchedrockkt_video_watched_atContacts and dealsWhen the recipient first started the video on the landing page.
Rockkt status changedrockkt_last_status_atContacts and dealsWhen the Rockkt status last changed.
Rockkt sourcerockkt_sourceContactsWhere in Rockkt this contact was first saved from, such as Rockkt One.
Rockkt pushed onrockkt_pushed_onContactsThe date Rockkt last saved this contact from Rockkt One.
Rockkt influencedrockkt_influencedDealsYes when a Rockkt send counts towards this deal (it came from the deal, the deal was open when it went, or the deal was created within your window after it).
Rockkt attributionrockkt_attributionDealsSourced when the deal was created after a Rockkt send, within your window; Influenced when it was already open, or the send came from it.
Rockkt spend (GBP)rockkt_spendDealsTotal net spend, in GBP, on the Rockkt sends that count towards this deal.
First Rockkt sendrockkt_first_send_dateDealsThe date of the first Rockkt send that counts towards this deal.

Rockkt gift status is one of: Draft saved, Waiting for approval, Address requested, Address confirmed, Declined, Approved, Dispatched, Delivered, Cancelled.

To build a workflow on it: in HubSpot, create a contact (or deal) workflow, choose “When filter criteria is met”, and pick a Rockkt property. For example: “Rockkt gift status is Delivered” to follow up after delivery, or “Rockkt landing page viewed is known” to tell the owner the moment their recipient looks.

ROI from your HubSpot deals

Rockkt can fill in your sends' outcomes from your HubSpot deals, so its ROI figures follow your pipeline without anyone logging them by hand. A Client Admin sets it up in Rockkt, on the Integrations page, under HubSpot, then ROI. It runs once a day, and Sync now runs it straight away.

It covers sends from the last 730 days that went or are going, whose recipient Rockkt can match to a HubSpot contact (a send from HubSpot, a person saved with Save to HubSpot, or the one contact with the recipient's email). A connection without the deals permission needs reconnecting once; Rockkt says so on the Integrations page.

Ready-made workflow recipes

Each uses the step “Send a Rockkt playbook”, so make the playbook in Rockkt first and mark it shared. In HubSpot, workflows are under Automation, then Workflows; choose Create workflow, then From scratch. The step is listed under Rockkt Gifts & Letters when you add an action. Turn the workflow on when you have reviewed it.

Demo booked: a note before the meeting

  1. Create a deal-based workflow.
  2. Trigger: when filter criteria is met, Deal stage is your demo stage (for example Appointment scheduled).
  3. Add Send a Rockkt playbook and choose a short personal note playbook (a handwriting-style letter design works well).
  4. Leave Address on Use my Rockkt setting. Choose Use the HubSpot address as it is only when your Rockkt setting is the same: a step can be stricter than your settings, never looser, and a looser one is skipped with a reason.

Deal stalled for 14 days: a nudge letter

  1. Create a deal-based workflow.
  2. Trigger: Last activity date is more than 14 days ago, and Is closed is false.
  3. Add Send a Rockkt playbook with a short “still thinking of you” letter playbook.
  4. Leave re-enrolment off, so one stalled deal gets one letter.

Closed won: a thank-you gift

  1. Create a deal-based workflow.
  2. Trigger: Deal stage is Closed won.
  3. Add Send a Rockkt playbook with a thank-you gift playbook.
  4. To have a Client Admin see each gift before it goes, set How it is sent to Wait for admin approval (your Rockkt setting must be approval or send straight away, since a step is never looser than your settings).

Meeting no-show: sorry we missed you

  1. HubSpot keeps a meeting's outcome on the meeting, not on the contact, so mark the contact your team's way: a static list such as “Missed meeting”, or a contact property you set.
  2. Create a contact-based workflow triggered by that list or property.
  3. Add Send a Rockkt playbook with a “sorry we missed you” letter playbook.

Recipient interested: more than the automatic task

  1. Rockkt already creates a call task for the owner (see A task when a recipient shows interest). Use this recipe only when you want more.
  2. Create a contact-based workflow. Trigger: Rockkt interested is known (or Rockkt gift status is a value you choose, such as Delivered).
  3. Add your own actions, for example enrol the contact in a sequence, notify a team, or create a deal.

Disconnecting

A Client Admin presses Disconnect HubSpot in Rockkt. Rockkt uninstalls the app from HubSpot, deletes its HubSpot access tokens and the owner matches, and stops writing to HubSpot. Your Rockkt orders keep showing that they came from HubSpot. The properties already written stay in HubSpot until you delete them there.

The data shared

HubSpot dataRockkt readsRockkt writesScopes
ContactsThe contact a workflow step or the Rockkt card runs on: name, email, company, job title, address and owner. To find a recipient’s contact (for the interest task and for ROI): a search by email. With Save to HubSpot on: a search by email or LinkedIn URL, and the contact’s company. A contact’s associated deals (for ROI) and tasks (so an interest task is never made twice).The Rockkt contact properties listed above. With Save to HubSpot on: first name, last name, job title, company, LinkedIn URL, email and office address, only where they are empty, and the owner only when the contact has none. A HubSpot task for the owner when a recipient shows interest, linked to the contact (and to the deal the send came from).
crm.objects.contacts.read
crm.objects.contacts.write
DealsThe deal a workflow step or the Rockkt card runs on, its owner and its associated contacts. For ROI: each deal on a recipient’s contact, with its pipeline, stage, amount, currency, created date, close date and whether HubSpot marks it won or lost; and your deal pipelines and their stages, so you can match them to Rockkt outcomes.The Rockkt deal properties listed above: the send’s status for a send that came from the deal, and for ROI, Rockkt influenced, Rockkt attribution, Rockkt spend (GBP) and First Rockkt send. Never a deal’s own fields.
crm.objects.deals.read
crm.objects.deals.write
CompaniesWith Save to HubSpot on: a company with the same website domain or name, so it is never created twice.With Save to HubSpot on: the company name and domain, only where empty, or a new company; and its link to the contact.
crm.objects.companies.read
crm.objects.companies.write
Contact and deal propertiesNothing.Creates the "Rockkt" property group and its properties, once, when you connect.
crm.schemas.contacts.write
crm.schemas.deals.write
Users (owners)Owner names and emails, to match each owner to a Rockkt user in your company.Nothing.
crm.objects.owners.read
WorkflowsThe step "Send a Rockkt playbook" and its settings, when a workflow runs it. The names of the workflows that started sends, to show them in Rockkt.Tells a waiting workflow when the recipient answered.
automation (optional)
Your sign-inWhich HubSpot account connected, so it belongs to one Rockkt company, and the account’s name (or, when it has none, its domain) to show in Rockkt.Nothing.
oauth

Rockkt asks for these scopes and no others: oauth, crm.objects.contacts.read, crm.objects.contacts.write, crm.schemas.contacts.write, crm.objects.owners.read, crm.objects.deals.read, crm.objects.deals.write, crm.schemas.deals.write, crm.objects.companies.read, crm.objects.companies.write, automation. HubSpot's access tokens are encrypted at rest, kept on Rockkt's servers only, and never sent to a browser or written to a log.

Support

Email hello@rockkt.com and a person will answer.

Privacy policy and terms