Moosewave integrations
Connect the tools your business already runs.
Bring ecommerce, CRM, forms, support, payments, analytics, and warehouse data into Moosewave. Keep customer profiles current, let useful events trigger the right journey, and inspect what each connection changed.
- Bring in
- Profiles & events
- Send out
- Audiences & signals
- Keep
- Run evidence
A direct answer
What is an email marketing integration?
An email marketing integration is a maintained connection between Moosewave and another system your business uses. It brings permitted customer records and useful events into the same profile so an order, form submission, or support change can update an audience or automation without a manual export. Where a connector supports it, selected data can also move back.
An integration moves evidence. It does not create consent, decide field ownership by accident, or make every source equally current.
Moosewave therefore treats the mapping, direction, run history, and recovery state as part of the connection—not setup details that disappear after authorisation.
From source to decision
Follow one customer signal from source to result.
A useful connection does more than move a row. It preserves the source, updates the mapped customer story, changes the decision that depends on it, and leaves enough evidence to explain the result.
evt_shopify_purchase- 01 · SourceOrder paid
Shopify supplies the configured source object and event identity.
- 02 · Evidence4 mapped facts
- Customer identity
- Order #1842
- Purchased products
- Payment and discount state
- 03 · CustomerProfile updated
The existing customer profile and order history are updated from the mapped commerce fields.
- 04 · DecisionEligibility changes
The cart reminder stops. The customer becomes eligible for the relevant post-purchase journey.
- 05 · ReceiptOutcome inspectable
The connection run records the source object, changes applied, and the continuing sync position.
The boundary travels with the signal. The purchase does not manufacture marketing permission; consent and suppressions still decide what may be sent.
Shopify purchase
A Shopify purchase can update the current order record, stop the relevant cart reminder, and make a post-purchase journey eligible while consent continues to govern messaging.
Typeform signup
A Typeform response can update a matching profile, preserve supplied permission evidence, recalculate a lead segment, and start an allowed welcome journey.
HubSpot lifecycle change
A HubSpot lifecycle change can refresh mapped CRM fields, update an audience, and change a nurture branch; selected two-way mappings only update matching existing records.
Zendesk support case
A Zendesk case can attach current support context to a profile and pause promotional follow-up while the case is open without overriding suppressions or consent.
Connection directory
Which tools integrate with Moosewave?
Browse a curated set of managed connectors, webhooks, APIs, automation bridges, and migration paths. Each card names the direction and supported data so a familiar logo never has to carry an unfamiliar promise.
Popular connections, then every path
Shopify
Customers, products, carts, orders, refunds, events, and selected profile writeback.
- Direction
- Two-way
- Category
- Commerce & payments
Stripe
Customers, checkouts, payments, invoices, subscriptions, disputes, refunds, and credit notes.
- Direction
- Into Moosewave
- Category
- Commerce & payments
Typeform
Forms, questions, responses, profiles, list membership, and submission events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
HubSpot
Contacts, selected lists and deals, lifecycle events, and selected existing-record writeback.
- Direction
- Two-way
- Category
- CRM & customer service
Zendesk
Requesters, tickets, ticket status, conversations, and support lifecycle events.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Recharge
Customers, subscriptions, charges, orders, cancellations, and subscription lifecycle events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
Meta Custom Audiences
Consent-eligible audience members, hashed identifiers, add/remove operations, and activation receipts.
- Direction
- From Moosewave
- Category
- Ads & acquisition
Snowflake
Auditable export manifests, ordered load plans, run history, and warehouse health evidence.
- Direction
- From Moosewave
- Category
- Analytics & warehouses
Inbound webhooks
Signed profile, event, list, and automation-trigger payloads with replay protection and run evidence.
- Direction
- Into Moosewave
- Category
- Developer & workflow tools
Zapier
Subscriber, list, campaign, approval, bounce, and automation workflows through configured recipes.
- Direction
- Two-way
- Category
- Developer & workflow tools
Twilio
Consent-gated SMS sends, inbound replies, delivery callbacks, sender state, and suppression handling.
- Direction
- Two-way
- Category
- Sending & messaging
Klaviyo
Profiles, lists, segments, events, and selected existing-record writeback, plus guided migration.
- Direction
- Two-way
- Category
- Marketing platforms
WooCommerce
Customers, products, variations, orders, coupons, refunds, subscriptions, and selected writeback.
- Direction
- Two-way
- Category
- Commerce & payments
BigCommerce
Customers, catalog products, orders, order items, coupons, transactions, and refunds.
- Direction
- Into Moosewave
- Category
- Commerce & payments
Adobe Commerce
Customers, products, orders, credit memos, refunds, and commerce lifecycle events.
- Direction
- Into Moosewave
- Category
- Commerce & payments
Wix Stores
Contacts, products, orders, payments, subscriptions, bookings, and ticket events.
- Direction
- Into Moosewave
- Category
- Commerce & payments
Squarespace Commerce
Contacts, products, orders, product details, and order lifecycle events.
- Direction
- Into Moosewave
- Category
- Commerce & payments
Square
Customers, catalog items, variations, orders, payments, locations, and refunds.
- Direction
- Into Moosewave
- Category
- Commerce & payments
PayPal
Transactions, customers, orders, captures, refunds, subscriptions, and invoices.
- Direction
- Into Moosewave
- Category
- Commerce & payments
Razorpay
Customers, orders, payments, refunds, and payment lifecycle events.
- Direction
- Into Moosewave
- Category
- Commerce & payments
Jotform
Forms, questions, submissions, profiles, list membership, and lead events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Gravity Forms
WordPress form entries, mapped fields, profiles, list membership, and lead events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
WPForms
Form definitions, entry fields, profiles, list membership, and submission events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Tally
Form responses, mapped profile fields, list membership, and submission events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Google Forms
Questions, response history, mapped profiles, lists, and submission events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
SurveyMonkey
Surveys, response history, mapped profiles, lists, and response events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Webflow
Webflow form submissions, profiles, list membership, and lead events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
WordPress
Subscriber capture, profiles, lists, and site events through the configured WordPress connection.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Unbounce
Landing-page leads, field labels, profiles, list membership, and submission events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Paperform
Forms, submissions, mapped profiles, list membership, and response events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Fillout
Forms, submissions, mapped profiles, list membership, and response events.
- Direction
- Into Moosewave
- Category
- Forms & lead capture
Salesforce
Contacts, leads, campaign members, tasks, lifecycle events, and selected existing-record writeback.
- Direction
- Two-way
- Category
- CRM & customer service
Pipedrive
People, organisations, deals, activities, lifecycle events, and selected existing-record writeback.
- Direction
- Two-way
- Category
- CRM & customer service
Zoho CRM
Contacts, leads, accounts, deals, lifecycle events, and selected existing-record writeback.
- Direction
- Two-way
- Category
- CRM & customer service
Microsoft Dynamics 365
Contacts, leads, accounts, opportunities, and mapped CRM lifecycle events.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Close
Leads, contacts, opportunities, activities, and mapped lifecycle events.
- Direction
- Into Moosewave
- Category
- CRM & customer service
HighLevel
Contacts, opportunities, appointments, tags, and mapped customer events.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Intercom
People, companies, conversations, tags, and support lifecycle events.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Gorgias
Customers, tickets, messages, connected order evidence, and support lifecycle events.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Freshdesk
Contacts, tickets, conversations, status changes, and support events.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Help Scout
Customers, conversations, mailbox events, and support signals through a configured bridge.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Front
Contacts, conversations, tags, and support events through a configured bridge.
- Direction
- Into Moosewave
- Category
- CRM & customer service
Yotpo
Reviews, reviewers, products, ratings, and review lifecycle events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
Judge.me
Reviews, reviewers, products, ratings, and review lifecycle events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
Okendo
Reviews, customers, products, ratings, and review lifecycle events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
LoyaltyLion
Members, points, tiers, rewards, referrals, and loyalty events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
Smile.io
Members, points, VIP tiers, rewards, referrals, and loyalty events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
Skio
Customers, subscriptions, orders, renewals, cancellations, and subscription events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
Chargebee
Customers, subscriptions, renewals, cancellations, orders, and billing events.
- Direction
- Into Moosewave
- Category
- Reviews, loyalty & subscriptions
AfterShip
Shipments, checkpoints, delivery state, exceptions, and fulfilment events.
- Direction
- Into Moosewave
- Category
- Shipping & fulfilment
ShipStation
Orders, shipments, carriers, tracking, and fulfilment events.
- Direction
- Into Moosewave
- Category
- Shipping & fulfilment
Shippo
Shipments, labels, carriers, tracking, and delivery events.
- Direction
- Into Moosewave
- Category
- Shipping & fulfilment
Easyship
Shipments, couriers, tracking, delivery state, and fulfilment events.
- Direction
- Into Moosewave
- Category
- Shipping & fulfilment
ShipBob
Orders, fulfilments, inventory, tracking, and delivery events.
- Direction
- Into Moosewave
- Category
- Shipping & fulfilment
EasyPost
Trackers, shipments, carriers, delivery state, and exception events.
- Direction
- Into Moosewave
- Category
- Shipping & fulfilment
Google Ads Customer Match
Consent-eligible audience members, hashed identifiers, removals, and request-status evidence.
- Direction
- From Moosewave
- Category
- Ads & acquisition
TikTok Audiences
Consent-eligible customer-file audiences, hashed identifiers, membership changes, and status evidence.
- Direction
- From Moosewave
- Category
- Ads & acquisition
LinkedIn Matched Audiences
Consent-eligible audience members, hashed identifiers, add/remove batches, and segment status.
- Direction
- From Moosewave
- Category
- Ads & acquisition
Snap Audiences
Consent-eligible audience members, hashed identifiers, membership changes, and request evidence.
- Direction
- From Moosewave
- Category
- Ads & acquisition
Facebook Lead Ads
Lead forms, lead responses, profiles, list membership, and acquisition events.
- Direction
- Into Moosewave
- Category
- Ads & acquisition
LinkedIn Lead Gen Forms
Lead forms, responses, profiles, list membership, and acquisition events.
- Direction
- Into Moosewave
- Category
- Ads & acquisition
Google Lead Form Extensions
Lead submissions, profiles, list membership, acquisition events, and import history.
- Direction
- Into Moosewave
- Category
- Ads & acquisition
Google Analytics 4
Mapped profile and event evidence from the configured analytics connection.
- Direction
- Into Moosewave
- Category
- Analytics & warehouses
Segment
Profiles, identities, traits, and behavioural events mapped into the customer record.
- Direction
- Into Moosewave
- Category
- Analytics & warehouses
RudderStack
Profiles, identities, traits, and behavioural events mapped into the customer record.
- Direction
- Into Moosewave
- Category
- Analytics & warehouses
Mixpanel
People and cohort/profile evidence from configured project exports.
- Direction
- Into Moosewave
- Category
- Analytics & warehouses
Amplitude
Profile and cohort evidence from configured behavioural exports.
- Direction
- Into Moosewave
- Category
- Analytics & warehouses
PostHog
People and mapped profile evidence from the configured PostHog project.
- Direction
- Into Moosewave
- Category
- Analytics & warehouses
BigQuery
Auditable export manifests, load-job plans, profile/event data, and run history.
- Direction
- From Moosewave
- Category
- Analytics & warehouses
Amazon Redshift
Auditable export manifests, load plans, profile/event data, and run history.
- Direction
- From Moosewave
- Category
- Analytics & warehouses
Postgres
Auditable export manifests, table plans, profile/event data, and run history.
- Direction
- From Moosewave
- Category
- Analytics & warehouses
Outbound webhooks
Signed subscriber, list, campaign, commerce, approval, and audit events with delivery history.
- Direction
- From Moosewave
- Category
- Developer & workflow tools
Make
Profiles, events, and workflow actions through configured scenarios, webhooks, and API keys.
- Direction
- Two-way
- Category
- Developer & workflow tools
n8n
Profiles, events, and workflow actions through self-hosted or cloud workflows.
- Direction
- Two-way
- Category
- Developer & workflow tools
Pipedream
Profiles, events, and workflow actions through configured components and API keys.
- Direction
- Two-way
- Category
- Developer & workflow tools
REST API & OpenAPI
Build a scoped custom integration against Moosewave’s documented HTTP surface.
- Direction
- Two-way
- Category
- Developer & workflow tools
TypeScript, Python & PHP SDKs
Build typed profile, event, list, segment, and automation workflows in your application.
- Direction
- Two-way
- Category
- Developer & workflow tools
Model Context Protocol
Expose scoped Moosewave tools to compatible agent clients with approvals and an activity trail.
- Direction
- Two-way
- Category
- Developer & workflow tools
Telnyx
Consent-gated SMS sends, inbound replies, delivery callbacks, sender state, and suppression handling.
- Direction
- Two-way
- Category
- Sending & messaging
Slack
Operator alerts, workflow notifications, approvals, and delivery-health signals.
- Direction
- From Moosewave
- Category
- Sending & messaging
Discord
Operator alerts, workflow notifications, and configured activity signals.
- Direction
- From Moosewave
- Category
- Sending & messaging
Microsoft Teams
Operator alerts, workflow notifications, approvals, and configured activity signals.
- Direction
- From Moosewave
- Category
- Sending & messaging
Amazon SES
Transactional delivery and SNS deliverability events through configured AWS sending infrastructure.
- Direction
- Into Moosewave
- Category
- Sending & messaging
Postmark
Server, message-stream, and deliverability evidence from the configured provider connection.
- Direction
- Into Moosewave
- Category
- Sending & messaging
Mailchimp
Audiences, profiles, tags, consent evidence, suppressions, templates, and campaign history.
- Direction
- Migration
- Category
- Marketing platforms
ActiveCampaign
Contacts, lists, tags, custom fields, consent evidence, automations, and campaign history.
- Direction
- Migration
- Category
- Marketing platforms
Customer.io
People, attributes, segments, message history, campaigns, and journey definitions.
- Direction
- Migration
- Category
- Marketing platforms
Brevo
Contacts, lists, attributes, consent evidence, templates, and campaign history.
- Direction
- Migration
- Category
- Marketing platforms
Kit (ConvertKit)
Subscribers, tags, segments, custom fields, sequences, and broadcast history.
- Direction
- Migration
- Category
- Marketing platforms
MailerLite
Subscribers, groups, fields, consent evidence, templates, automations, and campaigns.
- Direction
- Migration
- Category
- Marketing platforms
Omnisend
Contacts, segments, consent evidence, templates, automations, and campaign history.
- Direction
- Migration
- Category
- Marketing platforms
79 more available in this view
Direction is object-specific. The connection setup shows the exact objects, scopes, authentication method, historical lookback, and provider-side cleanup steps before you authorise it.
Shared customer evidence
What data can Moosewave integrations sync?
A connector’s object list is only half the answer. The useful question is what that evidence can change—and which decision it still cannot authorise.
On a small screen, swipe the table sideways to read every column.
| Data type | Evidence that can move | What Moosewave can do with it |
|---|---|---|
| Profiles and identities | Email, phone, external IDs, customer attributes, source bindings, and merge evidence. | Match activity to the right customer record without pretending two source records are automatically the same person. |
| Permission and suppressions | Consent purpose, source, captured wording, timestamps, channel preferences, opt-outs, and suppression state. | Decide whether an otherwise eligible person may receive a message or enter an advertising audience. |
| Forms and leads | Form IDs, response IDs, mapped answers, landing-page context, and acquisition source. | Update fields, add source-owned membership, qualify a lead, and trigger a permitted follow-up. |
| Commerce and subscriptions | Products, carts, orders, line items, discounts, payments, refunds, shipments, and subscription state. | Stop stale reminders and make the right cart, post-purchase, renewal, or win-back journey eligible. |
| CRM and support | Lifecycle stage, deals, account fields, tickets, status, conversations, and selected tags. | Keep sales and support context beside campaign decisions, with source-of-truth rules for mapped fields. |
| Reviews and loyalty | Reviews, ratings, points, tiers, rewards, referrals, and advocate activity. | Recognise customer contribution and time review, loyalty, or referral journeys from real events. |
| Audience destinations | Eligible members, purpose-specific consent, suppression decisions, provider request IDs, and exclusions. | Activate or remove allowed audience members while keeping an inspectable activation receipt. |
| Analytics and warehouses | Behavioural events, profile traits, export manifests, load plans, cursors, and run outcomes. | Bring useful evidence into the customer story or export governed records for analysis downstream. |
Connection lifecycle
How does a Moosewave integration work?
The connection begins with a job and ends with an operating record. Authorisation is one step in between—not the finish line.
- 01
Choose the job
Select the tool, objects, direction, and business outcome. A provider name alone is not a useful connection plan.
- 02
Authorise narrowly
Connect with the provider method and scopes required for the selected objects—no broader than the job needs.
- 03
Map the evidence
Assign identities, fields, permission evidence, source ownership, transforms, and conflict rules before records move.
- 04
Bring in history
Import the available lookback, preserve source identities, deduplicate overlaps, and review exceptions.
- 05
Continue from there
Use provider webhooks or scheduled continuation, depending on the connector, and resume from the last recorded position.
- 06
Operate the connection
Inspect runs, retry recoverable failures, pause deliberately, rotate access, or disconnect with cleanup guidance.
Quiet gaps made visible
How do you know a connection is working?
“Connected” only describes access. Health describes whether the expected data is arriving, being applied, excluded for a reason, or waiting for recovery.
Continuing work keeps a recorded position so a recoverable failure can retry or resume without turning the whole history into new work.
- 01Last successful run
The most recent point at which the connection completed its configured work without an unresolved error.
Answers: How fresh is this source?
- 02Records examined
How many source objects the run read, including records that correctly resulted in no change.
Answers: Did the expected scope get checked?
- 03Changes applied
Profiles, fields, memberships, events, or destinations that changed after mapping and permission rules.
Answers: What actually moved?
- 04Excluded or unchanged
Records intentionally spared because of suppression, consent, mapping, deduplication, or an unchanged value.
Answers: Why did some records not move?
- 05Retry and resume state
Whether work will retry, what needs attention, and the recorded position from which continuation resumes.
Answers: Will it recover without starting over?
- 06Provider cleanup guidance
Which local access was removed and whether an app, token, or webhook must also be removed in the provider console.
Answers: What remains after disconnect?
Permission and connection security
What happens to consent and connection security?
A strong integration preserves both access boundaries and customer boundaries. Provider credentials answer what Moosewave may read or write; customer consent answers what marketing may do with the evidence.
Credentials stay scoped
Use the provider method the connector requires—OAuth, an API-key reference, a signed webhook, or another supported credential—with only the scopes needed for the selected objects.
Mappings name ownership
Each field can identify its source of truth, transform, conflict policy, and deletion behavior instead of relying on whichever system wrote last.
Suppression wins
A connection may supply permission evidence; it cannot invent permission. Suppressions and purpose-specific consent remain authoritative for sends and audience activation.
Duplicates do not become new intent
Stable source identities and deduplicated retries keep replayed events from quietly becoming a second customer action.
Every workspace stays separate
Connections, credentials, mappings, runs, and audit history remain tenant-bound so one workspace cannot read or operate another workspace’s provider access.
Disconnect is explicit
Stop continuing work, remove locally managed access, and follow the recorded provider-side steps when external revocation or webhook cleanup is also required.
For the customer side of the boundary, read why email consent is a state and why the safest audience often begins with who the send leaves out.
A path beyond the directory
What if your tool is not listed?
Start with the direction and operating job. A managed connector is useful when provider-specific depth matters; a webhook, API, bridge, MCP tool, or migration may be the cleaner path for everything else.
Managed integrations
Use a provider-specific setup for mapped objects, historical import, continuing sync, run health, and lifecycle controls.
Best for
Commerce, CRM, forms, support, ads, and data
Inbound and outbound webhooks
Receive signed customer events or deliver supported Moosewave events with stable identities, retries, and delivery history.
Best for
Your application and event-driven tools
REST API and SDKs
Build a scoped connection with OpenAPI or the TypeScript, Python, and PHP SDK surfaces when you own both sides of the workflow.
Best for
Custom applications and internal data jobs
Automation bridges
Use configured Zapier, Make, n8n, or Pipedream workflows for tools whose best path is an automation recipe.
Best for
Long-tail operational tools
MCP tools and migrations
Let a compatible agent request governed Moosewave work through MCP, or use a verified migration when the job is a controlled move rather than an ongoing sync.
Best for
Agent workflows and platform changes
Compare an ongoing connection with a controlled email marketing migration, connect compatible AI tools through Moosewave MCP, or send application messages through the transactional email API.
One connected marketing system
The connection matters because the next decision can use it.
An order that lives only in a store, a ticket that lives only in support, or consent that lives only in a form leaves every downstream decision partially blind. Integrations give the rest of Moosewave a current, governed customer story.
Connected sending evidence continues into email deliverability, while Twilio and Telnyx workflows follow the channel-specific permission and operating rules explained in SMS marketing.
Questions about Moosewave integrations
Short answers about connector scope, Shopify, CRM writeback, historical data, consent, health, custom tools, and disconnecting.
What is an email marketing integration?
An email marketing integration is a maintained connection between Moosewave and another system your business uses. It brings permitted customer records and useful events into the same profile so an order, form response, CRM change, or support event can update an audience or automation without a manual export. Where a connector supports it, selected data can also move back.
Which integrations does Moosewave support?
Moosewave offers managed connectors, inbound and outbound webhooks, REST APIs and SDKs, automation bridges, MCP tools, and verified migration paths across commerce, payments, CRM, forms, support, reviews, loyalty, subscriptions, shipping, ads, analytics, warehouses, messaging, and marketing platforms. Each directory card names its connection path, direction, and data scope.
Does Moosewave integrate with Shopify?
Yes. The Shopify connection covers customers, products, carts, orders, discounts, refunds, commerce events, and selected existing-record writeback. A purchase can stop the relevant cart reminder and make a post-purchase journey eligible while consent and suppressions continue to govern messaging.
Does Moosewave integrate with HubSpot and Salesforce?
Yes. Moosewave can bring mapped CRM contacts, lifecycle fields, lists or campaign membership, deals or opportunities, and related events into the customer record. Selected mappings can update matching existing provider records; the supported object scope is shown before connection.
Are Moosewave integrations two-way?
Some are. Selected profile and audience writeback is available for Shopify, HubSpot, Salesforce, Pipedrive, WooCommerce, Zoho CRM, and Klaviyo. Writeback matches existing provider records, appends supported tags, and replaces explicitly mapped fields; it does not create missing provider records. Other connections are inbound, outbound, or migration-only.
Can Moosewave import historical customer data?
Yes, where the provider exposes the required history. The connection plan defines the lookback and objects, imports with stable source identities, records mapping exceptions, and then overlaps continuing sync carefully so the same source event is not applied twice.
How does Moosewave handle consent during an integration sync?
An integration can preserve permission evidence, but it cannot create permission that the source did not capture. Suppressions and purpose-specific consent take precedence. Audience activation checks the relevant consent and suppression state before eligible members are sent to supported advertising destinations, and exclusions remain visible in the run outcome.
Can I connect a tool that is not listed?
Often, yes. A tool may connect through a signed webhook, the REST API or an SDK, a configured automation bridge, or a controlled migration. The right path depends on whether data should enter Moosewave, leave it, continue in both directions, or move once during a platform change.
How can I monitor integration health?
The connection record shows the last successful run, records examined, changes applied, recoverable errors, retry state, and the point from which continuing work will resume. Run history and audit evidence make a quiet data gap diagnosable instead of invisible.
What happens when I disconnect an integration?
Disconnecting stops Moosewave synchronization and removes locally managed access. The connection record explains any provider-side credential, app, or webhook cleanup that must also be completed in the provider console. Historical evidence remains governed by the workspace’s retention and deletion controls.
What is the difference between an integration and a migration?
An integration is an ongoing connection that continues to exchange selected records or events. A migration is a controlled move from one platform to another with discovery, mapping, dry-run verification, cutover, and reconciliation. A migration may use a provider connection, but the operating goal is different.
Start with the system you cannot afford to leave out.
Explore a guided Moosewave workspace, or tell us which tool, objects, direction, and business outcome your connection needs.