Integrations
Connect Scrollmark to the rest of your stack — eCommerce, email, support, loyalty, and design tools.
Scrollmark talks to the tools you already use. Connecting them means that a comment in your Instagram inbox can trigger a Klaviyo flow, a Shopify order can show up as context on a DM, and a winning UGC post can be dropped into a Canva template without you copy-pasting anything.
Integrations vs. Social accounts vs. Webhooks
Three nearby settings pages get confused:
- Social accounts = Instagram, TikTok, Facebook (the things you post to)
- Integrations = everything else in your stack (Klaviyo, Shopify, etc.)
- Webhooks = custom HTTP endpoints you operate yourself
This page is about the middle one. For social connections see Connect your social accounts.
What you can connect today
From Settings → Integrations, Scrollmark shows a grid of connection cards. As of this writing, the built-in cards are:
Shopify
eCommerce: orders, customers, products as inbox context.
Klaviyo
Trigger Klaviyo flows from Scrollmark events; segment users by activity.
HubSpot
Sync contacts and surface CRM context in the inbox.
Postscript
Add SMS into your engagement flows.
Zendesk
Route tricky conversations to your existing support desk.
Iterable
Marketing automation: trigger campaigns from Scrollmark activity.
Gorgias
eCommerce-flavored helpdesk routing.
Attentive
SMS-first marketing automation.
Salesforce
Enterprise CRM context on every conversation.
LoyaltyLion
Reward your community for engagement.
Yotpo
Reviews, loyalty, and UGC.
Canva
Jump from an inspiring post into a branded Canva template.
Most integrations use OAuth — you'll be redirected to the other product's login, approve access, and get bounced back to Scrollmark. A few (like Klaviyo and Postscript) use API keys you paste into the card.
Connecting an integration
Open Settings → Integrations
From the Settings sidebar under your organization. You'll need at least Author; some integrations require Owner.
Click the card
Each card has a Connect button. For OAuth integrations, it opens a new tab. For API-key integrations, it opens a form where you paste the key and any other required fields.
Authorize or submit
For OAuth: sign in on the other side, approve the requested scopes, and you'll land back in Scrollmark with a success toast. For API keys: paste, click Save, and wait for the validation tick.
Confirm the connection
The card flips from "Connect" to a connected state showing the account name and a Disconnect option.
Notifications (Slack, email, SMS)
Notifications are configured in their own place: Settings → Notifications. Scrollmark can send alerts into:
- Email — to any address you own
- Slack — via a workspace connection and a channel picker
- SMS — for high-urgency alerts
Each channel has its own toggle page. You pick which event types get routed to which channel — for example, "VIP DMs" to Slack, "Daily digest" to email, "Crisis escalation" to SMS.
Webhooks (build your own)
If the off-the-shelf integrations don't cover your use case, you can
point Scrollmark at your own HTTP endpoint under Settings → Webhooks →
Create. You'll need manage_webhook permission (Owner, by default).
Scrollmark will POST JSON payloads to your URL whenever the events you pick happen — a new comment, a journey step completion, a tag applied, and so on. From there, it's on you to route to your stack.
Webhooks are the universal escape hatch
If you need to plug Scrollmark into a tool we don't officially support, a webhook and a glue service (Zapier, Make, n8n, or your own Lambda) is the fastest path.
Disconnecting an integration
Find the card
Back to Settings → Integrations, locate the card for the connected service.
Click Disconnect
You'll get a confirmation modal. Disconnecting a service immediately stops data flowing in both directions.
Check dependent journeys
If any live journey relies on data from that integration, it may stop producing results. Review Automation → Journeys for any that referenced the disconnected service and fix or pause them.
Reconnecting isn't free
Disconnecting and reconnecting a social or integration account can lose historical data that was linked to the old connection. If you're only trying to refresh tokens, look for the Refresh action before going the disconnect route.