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
- Companies with a Rockkt workspace (any Rockkt plan).
- HubSpot Professional or Enterprise, for workflows. On HubSpot Starter you can connect, but HubSpot has no workflows to start sends from.
How to connect
- In Rockkt, a Client Admin opens Integrations (in the menu) and presses Connect HubSpot.
- HubSpot asks a HubSpot Super Admin to approve the app. Only a Super Admin can install it.
- Back in Rockkt, finish in the same browser, signed in as the person who pressed Connect.
- 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
- When HubSpot starts a send: save a draft for the rep to check and send (the default), send it for a Client Admin's approval first, or send it straight away.
- The address: Recipient checks the HubSpot address (the default): we show them the address from HubSpot. They confirm it or change it. If HubSpot has none, they give one. Or Use the HubSpot address as it is: sent straight to the address on the HubSpot record, with no check. Rockkt never guesses an address, and never emails the recipient: the confirm link is yours to send.
- The monthly limit: the most sends HubSpot may start in a calendar month (UK time). It starts at 25.
- If the owner has no Rockkt user: do not send, or send it as a person you choose.
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.
- What is saved: first name, last name, job title, company name and LinkedIn profile link, plus an email or an office address only if Rockkt already found them for this person. Saving never runs a new lookup.
- No duplicates: Rockkt looks for the contact by email, then by LinkedIn profile link, and the company by website domain, then by name. A match is updated, never copied.
- Nothing overwritten: only empty fields are filled. The owner becomes the rep only when the contact has none. Contact and company are linked when the contact has no company yet.
- Marked: Rockkt source (Rockkt One) and Rockkt pushed on (the date).
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.
- Playbook: one of your company's shared playbooks in Rockkt. Its letter is filled in with the contact's first name, last name and company.
- How it is sent and Address: use your Rockkt settings, or something stricter for this step. A step can never be looser than your settings: if your settings say drafts, the step cannot send straight away, and it is skipped with a reason.
- The rep may change the playbook: for drafts.
- Wait until the recipient answers: when the recipient is asked to confirm, the workflow waits until they confirm or decline, or the link runs out, then carries on.
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.
- What reps see: the letters and gifts Rockkt has sent this person, newest first, each with its status in plain words, whether the landing page was viewed or “I'm interested” pressed, and a link to the send in Rockkt. On a deal, the person is the deal's primary contact. Open drafts for this person are listed too.
- Whose sends: a Client Admin sees every send the company made to this person. A rep sees their own sends, plus the ones a HubSpot workflow or the card made for this contact. Someone not matched to a Rockkt user sees only those HubSpot sends, which Rockkt already writes onto the record.
- Sending from the card: choose a shared playbook and “Send now” or “Save as a draft”, press Send, read what will happen and what it costs, and confirm. It is sent by the Rockkt user your HubSpot user is matched to, under your Rockkt settings: the address setting, approvals, and drafts if your setting says drafts. Every normal Rockkt check, credit and price applies.
- The monthly limit: a send from the card is a person's choice, not an automated one, so it does not count towards the monthly limit for HubSpot workflows.
- Not matched yet: the card says so. A Client Admin matches HubSpot users to Rockkt users in Rockkt, on the Integrations page, under HubSpot.
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:
- For every send started from HubSpot (by a workflow or from the Rockkt card): the send's status, links and landing page activity, on its contact, and on its deal when it came from one. Updates arrive within about ten minutes.
- With Save to HubSpot: where a contact was saved from, and when.
- For ROI: on each deal a Rockkt send counts towards (see ROI from your HubSpot deals, below).
| Property | Internal name | On | What it holds |
|---|---|---|---|
| Rockkt gift status | rockkt_gift_status | Contacts and deals | Where the latest Rockkt send is. |
| Rockkt last order | rockkt_last_order_ref | Contacts and deals | The reference of the latest Rockkt send. |
| Rockkt last playbook | rockkt_last_playbook | Contacts and deals | The Rockkt playbook the latest send used. |
| Rockkt confirm link | rockkt_confirm_link | Contacts and deals | The link the recipient uses to confirm or give their address, while Rockkt is waiting for them. |
| Rockkt landing page | rockkt_landing_page_url | Contacts and deals | The landing page that goes with the latest Rockkt send. |
| Rockkt landing page viewed | rockkt_landing_page_viewed_at | Contacts and deals | When the recipient first opened the landing page. |
| Rockkt interested | rockkt_interested_at | Contacts and deals | When the recipient first pressed "I'm interested" on the landing page. |
| Rockkt video watched | rockkt_video_watched_at | Contacts and deals | When the recipient first started the video on the landing page. |
| Rockkt status changed | rockkt_last_status_at | Contacts and deals | When the Rockkt status last changed. |
| Rockkt source | rockkt_source | Contacts | Where in Rockkt this contact was first saved from, such as Rockkt One. |
| Rockkt pushed on | rockkt_pushed_on | Contacts | The date Rockkt last saved this contact from Rockkt One. |
| Rockkt influenced | rockkt_influenced | Deals | Yes 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 attribution | rockkt_attribution | Deals | Sourced 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_spend | Deals | Total net spend, in GBP, on the Rockkt sends that count towards this deal. |
| First Rockkt send | rockkt_first_send_date | Deals | The 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.
- Which deals count: for a send to a HubSpot contact, a deal is Influenced when the send came from it, or when it was already open on that contact when the send went. It is Sourced when it was created on that contact after the send, within your window. A deal closed before the send, or created after the window, does not count.
- Your window: 90, 180 or 365 days, or any number of days from 30 to 730. It starts at 180.
- Won and lost are automatic: they come from HubSpot's own won and lost on the deal. A won deal is recorded with its amount and close date, so it needs an amount in HubSpot.
- Every other stage is your choice: match each stage to Working, Meeting booked, or Leave alone. Use suggested matches fills in HubSpot's standard stages (Appointment scheduled and Presentation scheduled as Meeting booked; Qualified to buy, Decision maker bought-in and Contract sent as Working) and leaves any other stage alone.
- A person's outcome is never overwritten: when somebody in your team has logged an outcome for a send in Rockkt, Rockkt leaves that send alone.
- Written on the deal: Rockkt influenced, Rockkt attribution (Sourced or Influenced), Rockkt spend (GBP) and First Rockkt send.
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
- Create a deal-based workflow.
- Trigger: when filter criteria is met, Deal stage is your demo stage (for example Appointment scheduled).
- Add Send a Rockkt playbook and choose a short personal note playbook (a handwriting-style letter design works well).
- 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
- Create a deal-based workflow.
- Trigger: Last activity date is more than 14 days ago, and Is closed is false.
- Add Send a Rockkt playbook with a short “still thinking of you” letter playbook.
- Leave re-enrolment off, so one stalled deal gets one letter.
Closed won: a thank-you gift
- Create a deal-based workflow.
- Trigger: Deal stage is Closed won.
- Add Send a Rockkt playbook with a thank-you gift playbook.
- 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
- 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.
- Create a contact-based workflow triggered by that list or property.
- Add Send a Rockkt playbook with a “sorry we missed you” letter playbook.
Recipient interested: more than the automatic task
- 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.
- Create a contact-based workflow. Trigger: Rockkt interested is known (or Rockkt gift status is a value you choose, such as Delivered).
- 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 data | Rockkt reads | Rockkt writes | Scopes |
|---|---|---|---|
| Contacts | The 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 |
| Deals | The 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 |
| Companies | With 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 properties | Nothing. | 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 |
| Workflows | The 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-in | Which 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.