Your Data, Explained: How Shippy Works With HubSpot

Before installing a shipping app, you want to know which records it reads, what it adds to your CRM, and what your admin can configure. Those are sensible questions to bring to an app review, especially when your IT or compliance team needs specifics before approving an installation.

Shippy by Dijy is a native HubSpot shipping label app. Here's a practical look at its documented interaction with HubSpot and the settings your team controls. For questions beyond these details, contact Dijy directly.

Review the Connection Before Installing Shippy

Shippy connects through HubSpot's OAuth agreement, which your admin reviews before selecting Connect app. That agreement is the place to examine the requested access during installation.

Give the person responsible for app approval time to review it. If a permission raises a question, bring it to Dijy before connecting. You can use our installation guide alongside your internal approval process to keep the setup steps and your review aligned.

The feature summary below explains documented uses of HubSpot data. It doesn't replace reviewing the OAuth agreement or requesting answers about specific permissions.

What Shippy Writes to HubSpot

Installation adds a custom “Shippy” pipeline on HubSpot's Orders object and a Shippy property group across contacts, companies, deals, tickets, orders, and custom objects. These additions are part of what your admin should expect to see in the account.

The property group includes Recent Shippy Tracking Number, Recent Shippy Tracking Status, and the tracking Status Detail field. Shippy writes shipment information into these fields, making that information visible within your CRM.

For your internal review, list the pipeline and property group separately. The pipeline organizes shipping information on Orders; the properties carry tracking information on the listed record types. Our fields guide gives your admin a reference for these additions.

What Shippy Reads From Your Records

Shippy reads recipient details from default HubSpot fields or from custom fields your admin selects in Property Mapping. If your team keeps shipping details in dedicated properties, those mappings identify the fields Shippy uses for recipient information.

Review your Property Mapping choices with the people who maintain your CRM. Agree on which fields contain the recipient details you intend to use, and record those choices in your setup notes.

Shippy also reads deal line items for packing slips. Include that in your review alongside recipient information, so your checklist reflects both shipping details and the product information used for those slips.

What Your Admin Controls

Your admin controls which Shippy app cards appear on which objects, which carriers are enabled, and which fields are mapped. These are distinct setup decisions, each worth reviewing before your team starts using the app.

For app cards, decide where your team needs the shipping interface. For carriers, confirm which options you want enabled. For field mapping, agree on the source of recipient details rather than relying on an undocumented assumption about your CRM setup.

Keep configuration choices separate from permission conclusions. Choosing where a card appears or which recipient fields are mapped isn't a substitute for reviewing the OAuth agreement. Ask Dijy if your approval process needs a more detailed explanation of how configuration and requested access relate.

What You Can Review in Shippy Settings

Shippy Settings shows shipment history, drafts, billing history, and packing slips. Payment methods are managed in Shippy's billing settings. These are the places to review the corresponding activity and configuration.

For a practical handoff, identify who on your team will review shipping activity and who will manage billing details. Walk those people through the relevant settings so they know where to look when questions come up.

Information appearing in a settings screen describes what you can review there. It doesn't, by itself, answer questions about underlying storage or retention. Bring those questions to Dijy if they're part of your approval checklist.

Supporting Details to Include in Your Review

Three supporting details belong in your review: Google Maps address autocomplete, public logo links, and Shippy Connect's account-wide login. Naming them explicitly helps your team ask focused questions before setup.

Address autocomplete uses Google Maps. For packing slip logos, Shippy pulls the image from a public link your admin provides. Choose the intended logo image and confirm that the link is suitable for public access.

Shippy Connect uses one login shared across the HubSpot account, rather than a unique login for each user. Include that detail in your team's access review. A shared account login doesn't establish that every user shares the same active session.

Ask About the Business Associate Agreement

The Mega Shipper plan includes a Business Associate Agreement, or BAA. If your organization needs one, ask Dijy for the agreement and have the appropriate people review it.

Keep the claim specific: a BAA is included with Mega Shipper. That fact alone isn't a conclusion about your organization's compliance requirements or how a particular shipping process should be configured. Bring your requirements to Dijy for a direct conversation.

Bring Your Data Questions to Dijy

Use these documented details to start your review, then send us the questions your team still needs answered. If you need specifics about encryption, storage locations, retention, certifications, or compliance requirements, request those details directly rather than treating this overview as an answer.

Ready to talk through your checklist? Get in touch with Dijy and share the questions your admin, IT, or compliance team has about Shippy. Tell us which detail you're reviewing so we can address the actual question. We're here to work through it with you.