Signals come from wherever your customers already are.
ConvoHut does not need a new source of truth. It reads the systems you already run — your store, your sheet, your ad account, your CRM — turns what it finds into contacts and signals, and triggers journeys from them.
How does ConvoHut get my customer data?
Through connections to systems you already use. A Shopify app connection, a spreadsheet, an ad account, a CSV upload, or a webhook for anything custom. Data is pulled into contacts and signals; ConvoHut does not ask you to migrate anything.
Key takeaways
- Three objects to understand: contacts, signals and catalogue.
- A signal without a matched contact cannot be messaged — identity resolution matters more than volume.
- Consent travels with the contact and is checked before any journey sends.
- Anything not natively supported can arrive by webhook.
The data model, in three objects
Every journey you build is some combination of these. Understanding them makes the rest of the platform obvious.
Contacts
One record per human. Phone number, consent status, attributes and lifecycle stage. Everything else hangs off this.
Signals
Timestamped things a contact did — cart created, product viewed, order placed, form submitted, appointment booked. Journeys trigger on these.
Catalogue
Your products, with images, variants, price and stock, so a reply can answer a real question about a real item.
Where signals can come from
Availability is stated honestly. Anything marked coming soon is not in the product today — do not plan around it, and ask us where it actually sits before you commit.
| Source | What it brings | Status | Setup |
|---|---|---|---|
| Shopify | Carts, orders, customers, products, checkouts | In build for launch | App connection |
| WooCommerce (roadmap) | Carts, orders, customers, products | In build for launch | Plugin connection |
| Webhook / REST API | Any event you can post to us | In build for launch | Developer |
| Zapier | Anything Zapier connects to | In build for launch | No-code |
| CSV import | Contacts and historical orders | In build for launch | Upload |
| Google Sheets | Contacts, leads and rows as events | Coming soon | No-code |
| Meta lead ads | Lead form submissions from Facebook and Instagram | Coming soon | Ad account link |
| HubSpot, Zoho, Salesforce | Contacts, deals and lifecycle stage | Coming soon | OAuth |
| Make | Anything Make connects to | Coming soon | No-code |
Two things that decide whether this works
Identity
A cart event with no phone number attached cannot start a conversation. The share of your traffic you can actually identify sets the ceiling on every journey, and it is worth measuring before you judge a journey's performance.
Logged-in customers, checkout starts and known leads resolve cleanly. Anonymous first-time browsers usually do not.
Consent
WhatsApp is a permission channel. Consent is stored on the contact, checked before every send, and honoured immediately on opt-out.
If opt-in was never captured, no journey design fixes it. Getting a consent mechanism into your checkout or form is usually the highest-value hour of the whole setup.
Questions this raises
Do I have to move my data into ConvoHut?
No. Connections read from the systems you already run. Nothing is migrated, and your store or CRM remains the source of truth.
What if my platform is not listed?
Use the webhook or REST endpoint. If you can post an event when something happens, ConvoHut can trigger a journey from it.
Can I use a Google Sheet as a source?
That connector is on the roadmap rather than in the product today. Until it ships, a CSV import or a Zapier step covers most spreadsheet workflows.
How fresh is the data?
Native connections stream events as they happen, which is what makes a twenty-minute cart trigger meaningful. Batch sources like a CSV are only as fresh as the last upload.
Does data flow back to my store?
The primary direction is into ConvoHut. Opt-out state is the case worth syncing back, and it should be part of your setup plan.
Who can see my customer data?
Your workspace users, with role-based permissions. See the security and data page for what is currently implemented and which certifications are still in progress.
The whole series
Five pages. Read them in order and you will know exactly what ConvoHut does, what it does not do, and what it will cost you.
Bring one data source and one journey.
That is all a pilot needs. We connect it with you and agree the success metric before anything goes live.