Use the purpose, data, and requirements of each integration to decide which ones fit your business.
Integrations at a glance.
WhatsApp and Meta
Handle conversations, import leads from Meta ads, and schedule posts for connected social media accounts.
Data. Messages and sender details, lead form fields, and the text and media in scheduled posts.
Requirements. A connected WhatsApp Business account, or an authorized Meta page and a linked lead form for the ads.
Google Ads and reviews
Manage ads and respond to Google reviews.
Data. Campaigns and metrics from the ads account, and reviews and replies for the connected business profile.
Requirements. A connected Google Ads account or an authorized Google Business Profile.
Google and Outlook calendars
Sync appointments between CleverHub and the connected calendar.
Data. Depending on the direction of the sync, this includes the time range, appointment name, and description.
Requirements. An authorized Google or Outlook calendar. Agree on which appointment details to transfer before syncing.
Telegram
Receive configured notifications in a Telegram chat.
Data. The title and message body. If the notification includes a telephone number, that is sent too.
Requirements. A configured Telegram bot and a destination chat the bot has permission to send messages to.
REST API and webhooks
For example, check calendar connection status or receive new leads from a Meta ad.
Data. The calendar query returns connection status. For Meta, the lead event comes first, followed by the authorized form fields.
Requirements. An authorized CleverHub account for REST calls. For Meta, a configured integration that verifies webhook requests.
Payments and billing
Connect Stripe payments and, depending on setup, provide TWINT payment instructions, a QR bill, or a supported electronic invoice.
Data. Amounts and references are among the data used for payments. Invoices use the required billing and payment details.
Requirements. A suitable merchant account or payment profile and up-to-date billing details. The available format depends on your setup.
Practical workflows with REST and webhooks
An authorized REST request can read leads in the selected work context. This helps explain how a specific sync would work. Calendar status is another example. The request returns the Google or Outlook connections configured for the signed-in account. For either use, decide in advance which account will access it and what information it needs.
Incoming webhooks report events. Meta Lead Ads, for instance, reports a new form submission. CleverHub can then retrieve the authorized form fields through the configured Meta connection. WhatsApp reports incoming messages for the connected business number. For Stripe Checkout, a confirmed payment event can update the linked invoice. Each integration has its own requirements.
How to choose your first sync
Write down the task your team currently maintains in two places. Identify the system of record and decide where the other system needs to see the current state. Syncing appointments has different implications from importing new leads. Use a sample appointment or test form field to discuss the details before connecting live accounts.
Frequently asked questions
What accounts do I need for calendar sync?
You need an authorized Google or Outlook calendar. Decide which calendar to connect to CleverHub and which appointment details your team should be able to see through it.
What’s the difference between a REST call and a webhook?
With REST, an authorized application requests existing information. With a webhook, the connected service sends an event such as a new Meta lead or a completed Stripe checkout.
How does form data from a Meta ad get to CleverHub?
A configured Meta integration receives the lead notification. The authorized form fields are retrieved through the corresponding connection. Check the mapping when you set up a new ad form.
What information can a Telegram message contain?
The configured notification contains a title and a message body. Some notifications also include a phone number. Check who can access the selected chat.
Can every payment be matched automatically?
Stripe matching requires a checkout session correctly linked to the invoice and a confirmed payment. The other payment and billing features that apply depend on your configured profile.