STEP 1
Connect Apps
Authorize HubSpot, Google Sheets, and other providers for this mail owner.
Connections
Choose a Mail Owner on the left to connect apps, manage destination defaults, and review activity.
Pit Stops decide which events are sent and where they go. This page manages the connected accounts and default delivery settings those Pit Stops can use.
No connection activity yet.
Connected apps and destination defaults are available to this mail owner’s Pit Stops. Events are configured inside each Pit Stop.
Public Integrations Overview Start a Loop with the API
Build your own integration: When a native app is not enough, POST JSON to the UOCL Loop Start webhook from your server and deliver results with webhook feeds. Start a Loop with the API →
STEP 1
Authorize HubSpot, Google Sheets, and other providers for this mail owner.
STEP 2
Save reusable Email and Webhook starting values for new Pit Stop destinations.
STEP 3
Each Pit Stop chooses events, fields, mappings, and which destinations receive them.
Pit Stops own event delivery. This page keeps the connected accounts and defaults those Pit Stops can use.
Reusable starting values for new Email and Webhook destinations created inside Pit Stops. Saving defaults does not send events or create active routes.
A Pit Stop can override these values without changing the mail-owner defaults.
These values pre-fill new Email destinations created inside Pit Stops.
These values pre-fill new Webhook destinations inside Pit Stops. Saving defaults does not send any events.
See every connected account and configuration for this mail owner — what it is used for, whether it is healthy, and what you can edit.
Connected App = authorized provider account. Configuration = a specific sheet, CRM object, email destination, or webhook beneath that account.
Select a mail owner to view connections and configurations.
Connect Indemption directly to sales and communication tools using secure OAuth. Pit Stops choose which events use these apps.
HubSpot, Google Sheets, and Salesforce OAuth are live. Slack is coming soon.
Map Indemption events (IV tracking, QR scans, Pit Stop leads, wallet activity) to HubSpot contact updates and notes.
HubSpot may show an unverified app warning while Indemption Connections is in beta.
Mail Owner: —
Choose a mail owner first.
Connect Salesforce Contacts to Indemption for mailing-list imports, field mapping, and approved CRM write-back workflows.
Salesforce contact import and write-back features are currently in beta.
Mail Owner: —
Choose a mail owner first.
Connect Slack to post scan, lead, and Wallet Pass alerts into sales channels.
Connect a Google account, then add Sheet configurations for mailing lists or event history.
Mail Owner: —
Choose a mail owner first.
Connect Indemption projects to ServiceTitan marketing campaigns so QR scans, Pit Stops, wallet saves, and redemptions can be attributed back to the right campaign.
Additional CRM destinations can be added based on beta customer demand.
Review connection administration and Pit Stop event deliveries for this mail owner.
Activity reflects Pit Stop execution and connected-app health — events are not configured on this page.
| Time | Direction | Event | Connection | Source | Status | Details |
|---|---|---|---|---|---|---|
| Loading activity… | ||||||
Outcomes are results received from connected providers or event processing — such as HubSpot updates, webhook responses, wallet redemptions, and email delivery results.
This tab does not configure event routes. Pit Stops own outbound event delivery; outcomes will surface results here when available.
These are future result channels. They are not active route builders and cannot be created from this page yet.
Let POS systems, staff tools, mobile apps, kiosks, or redemption pages validate and redeem Wallet Passes.
Receive sale, coupon, appointment, or closed-lead events from outside systems.
Match online orders, discount codes, and customer purchases back to physical campaign scans and wallet offers.
Receive transaction, appointment, or customer outcome data from POS, CRM, booking, or customer management systems.
These are the most common ways teams send business results back to Indemption for attribution.
Validate and redeem Wallet Passes from a POS system, staff tool, kiosk, or redemption page.
Passive examples
Send sale or transaction events back to Indemption so revenue can be tied to a campaign, project, Pit Stop, or mailing record.
Passive examples
Send booked or completed appointment events back so campaigns can be measured beyond the first scan.
Passive examples
Send closed-won, closed-lost, or qualified lead outcomes back into Indemption.
Passive examples
Create and manage keys for Loop Start and webhook integrations. Full control lives on the API Keys tab.
Use the API Keys tab to create, rotate, and delete mail-owner scoped keys (bw_live_…). Send them as x-api-key.
Create, rotate, and delete keys for this Mail Owner. Keys use the format bw_live_… and are sent as the x-api-key header. The full secret is shown only once at create or rotate.
Create a key for Loop Start webhooks and other inbound integrations for this Mail Owner.