Logbook setup guide for HubSpot
Logbook is an app built for the HubSpot platform. It keeps the full change history of key properties of your HubSpot deals, contacts and companies, and lets you read and download it as CSV. HubSpot itself keeps up to 20 past values of a deal or company property and 45 of a contact property; Logbook keeps every value from the day you install it.
Use it to audit your pipeline (which deals moved back, slipped or changed amount, and who did it), to track owner reassignments, to report on lifecycle stage and lead status over time, and to find the values a bad import or workflow overwrote.
- 1. What Logbook does
- 2. Install Logbook and connect your HubSpot account
- 3. Configure Logbook
- 4. Use Logbook
- 5. Free trial and Logbook Pro
- 6. Disconnect Logbook
- 7. Uninstall Logbook
- 8. What happens to your data
- 9. Troubleshooting
What Logbook does
After you install it, Logbook works on its own. It records changes to these properties:
| Object | Properties |
|---|---|
| Deals | Deal stage, pipeline, deal owner, amount, close date |
| Contacts | Lifecycle stage, lead status, contact owner |
| Companies | Lifecycle stage, company owner |
- Automatically: right after install it reads the history HubSpot still keeps for every record. Then, once a day, it reads the history of every record that changed and stores the new values.
- On request: a Logbook page inside HubSpot shows the changes of one property over a period you choose, and downloads them as CSV.
Logbook only reads. It never creates, changes or deletes anything in your HubSpot account, and it never reads contact names, email addresses or phone numbers.
Install Logbook and connect your HubSpot account
Installing Logbook and connecting your HubSpot account is one step: there is no separate Logbook account or password. To install, you need to be a Super Admin in your HubSpot account or have App Marketplace access permission.
Step 1. Start the install
Click Install on the Logbook listing in the HubSpot App Marketplace, or Install Logbook on jimapps.dev/logbook.
Step 2. Choose your HubSpot account
Sign in to HubSpot if asked. If you have access to more than one HubSpot account, choose the one you want Logbook to record, then click Choose account. Check the account name and ID before you continue: Logbook records only the account you choose here.
file: /logbook/img/install-choose-account.webp
Step 3. Review and approve the access Logbook asks for
HubSpot shows the access Logbook requests. All of it is read-only:
| Scope | What Logbook uses it for |
|---|---|
crm.objects.deals.read | History of deal stage, pipeline, owner, amount and close date; deal names in the CSV |
crm.objects.contacts.read | History of lifecycle stage, lead status and owner of contacts |
crm.objects.companies.read | History of lifecycle stage and owner of companies; company names in the CSV |
crm.objects.owners.read | Email addresses of owners and of the users who made each change, so the CSV names people instead of IDs |
oauth | Added by HubSpot to every app; lets Logbook keep its connection |
HubSpot grants read access to whole records, but Logbook stores only the tracked properties listed above. Click Connect app to approve.
file: /logbook/img/install-consent.webp
Step 4. Installation confirmed
HubSpot sends you to a page on jimapps.dev that confirms Logbook is installed. From there you can open Logbook in HubSpot or look at Logbook Pro. Logbook now appears in your HubSpot account under Settings → Integrations → Connected Apps.
file: /logbook/img/install-done.webp
Step 5. The first read
Logbook starts reading the history HubSpot keeps for every deal, contact and company. In a small account this takes minutes; in an account with hundreds of thousands of records it takes a few hours. You do not need to keep anything open. While it runs, the Logbook page in HubSpot says the first read is in progress and shows changes as they arrive.
Configure Logbook
There is nothing to configure. The list of tracked properties is the same in every account, and the daily read runs on its own. Logbook works with the stages, pipelines, lead statuses and owners you already have, including custom pipelines and stages: their names are read from HubSpot each time you open or download changes, so renamed stages show their current name.
Use Logbook
Open Logbook in HubSpot
In HubSpot, click the Marketplace icon in the top navigation bar and choose Logbook in the menu. You can also use the Open Logbook in HubSpot button on the page you saw after installing, and bookmark the page it opens.
file: /logbook/img/use-open.webp
Read the changes
- At the top, Logbook shows since when it has been recording and how many values it holds.
- Choose a Property, for example "Deals: deal stage".
- Choose a Period: last 30 days, last 90 days, last 12 months or all time.
- The table shows the latest 50 changes: when (UTC), the record with a link to it, the value before (From), the value after (To), and who changed it. When no user made the change, Logbook shows the source instead: workflow, import, API, integration, or HubSpot itself.
file: /logbook/img/use-page.webp
Download the CSV
Click Download CSV above the table. The file holds every change of the chosen property in the chosen period, not only the 50 shown. The download link is valid for 15 minutes; after that, click the button again. The file has one row per change:
| Column | Contents |
|---|---|
record_id | HubSpot record ID |
record_name | Deal or company name. Empty for contacts (Logbook does not read contact names) and for records deleted since |
record_url | Link to the record in HubSpot |
property | Internal name of the property, for example
dealstage |
changed_at | Date and time of the change, UTC |
from, to | Value before and after the change, with stage, pipeline and option labels, and owners as email addresses |
source | Source as reported by HubSpot, for example
CRM_UI, WORKFLOW, IMPORT, API |
changed_by | Email address of the HubSpot user who made the change, if a user made it |
HubSpot also records a property being set to the value it already had; Logbook leaves those
out, so every row is a real change. To restore old values, filter the CSV, keep
record_id and from, and import them into HubSpot.
file: /logbook/img/use-csv.webp
Free trial and Logbook Pro
For 14 days after install everything in Logbook is open: the page and the CSV cover the whole recorded history, and the Logbook page in HubSpot shows how many trial days are left. After the trial Logbook keeps recording, and Logbook Pro keeps the history open to view and download: $19 a month or $180 a year per HubSpot account.
- Click Subscribe in the trial notice on the Logbook page, or go to jimapps.dev/logbook/upgrade.
- Check the HubSpot account ID. It is filled in when you come from Logbook; otherwise you find it in HubSpot in the account menu at the top right.
- Choose monthly or yearly and complete the checkout. Payments are handled by Paddle, our merchant of record.
Pro is active within a minute, and the whole history recorded so far becomes available, including what was recorded after the trial ended. To cancel, write to contact@jimapps.dev from the email address you paid with, or uninstall Logbook: uninstalling cancels the subscription automatically.
Disconnect Logbook
Logbook has no account of its own, so the only connection is the app installed in your HubSpot account. To disconnect your HubSpot account from Logbook, uninstall Logbook as described in the next section. There is no way to pause recording while keeping the app installed.
What happens to your data when you disconnect: Logbook loses access to your account, all history Logbook stored for that account is deleted, and a Logbook Pro subscription is cancelled. Your HubSpot records are not touched: Logbook never wrote anything to them. Details in What happens to your data.
Uninstall Logbook
You need to be a Super Admin or have App Marketplace access permission.
- In HubSpot, click the settings icon in the top navigation bar.
- In the left sidebar, go to Integrations → Connected Apps.
- Find Logbook, click Actions, then Uninstall.
- In the dialog box, type uninstall and click Uninstall.
file: /logbook/img/uninstall.webp
HubSpot's own article on this: Connect apps to HubSpot.
What happens to your data
| When | What happens |
|---|---|
| You uninstall | HubSpot revokes Logbook's access. The Logbook page disappears from your account. |
| Within a day | At its next scheduled read, Logbook sees that its access was revoked and deletes everything it stored for your account: the recorded history and the connection details. A Logbook Pro subscription is cancelled; the period you already paid for is not charged again. |
| In HubSpot | Nothing changes. Your records, properties and HubSpot's own property history stay as they are. |
Deleted history cannot be recovered. If you may need it later, download the CSV of each property before you uninstall. If you install Logbook again later, it starts over from the history HubSpot still keeps at that moment. To have your data deleted right away, write to contact@jimapps.dev. More in the privacy policy.
Troubleshooting
"Logbook could not load" with "Logbook is not connected to this portal"
The install did not finish on Logbook's side, for example because the browser was closed before the confirmation page opened. Install Logbook again from jimapps.dev/logbook; nothing in your HubSpot account is affected.
"This download link has expired"
Download links work for 15 minutes. Go back to the Logbook page in HubSpot and click Download CSV again.
"No changes in this period"
The property did not change in that period, or the first read has not reached those records yet.
A value shows as a number instead of a name
The stage, pipeline or option was deleted in HubSpot, so its name no longer exists. Logbook shows the internal ID that HubSpot stored.
Limits
- History starts with what HubSpot still kept on the day you installed Logbook.
- Only the ten properties listed above are tracked; custom properties, tickets and custom objects are not.
- New changes appear after the next daily read. A value is missed only if one property of one record changes more than 20 times between two daily reads.
Support
Write to contact@jimapps.dev. Response times and what to include are on the support page.