Everything a Linkubit workspace connects to today — four messaging channels, two ad networks, Apollo, monday.com and Zoho CRM, two payment rails, webhooks — and the CRMs and stores planned next.
Everything here is connected in your own name — your WhatsApp number, your domain, your ad accounts, your Apollo workspace, your payment gateway. Linkubit holds a grant, not a copy, and what happens in the conversation reaches your other tools by signed webhook. The CRMs and stores below are next, in the order people ask for them.
The channels the assistant answers on and campaigns go out over. Each is connected in your own name — your number, your domain, your Page.
Your number on Meta's Cloud API, connected through Embedded Signup.
Connect an existing WhatsApp Business number or a new one from the settings screen; the assistant replies inside the 24-hour window and campaigns go out as approved templates. Meta bills your own account for delivery, with nothing added on top.
Settings › Channels › WhatsApp · More
Send and receive from an address on a domain you verify.
Verify a domain, and outbound mail leaves from it with a Reply-To the product can receive on, so a customer's answer lands in the same inbox as their WhatsApp messages. Bounces and complaints suppress the address automatically.
Settings › Sending · More
Replies to direct messages on a professional account.
Connect the Instagram account attached to your Facebook Page and DMs arrive in the shared inbox for the assistant or a person to answer. Reply-only, because Meta permits no business-initiated messages on Instagram — there is no Instagram campaign, and there never appears to be one.
Settings › Channels · More
Messages to your Page, answered in the same inbox.
Connect the Page and Messenger conversations join the queue with WhatsApp, email and Instagram. Reply-only, for the same reason as Instagram.
Settings › Channels · More
Ad accounts read in for spend and leads, used to build paused campaigns, and told which leads turned into customers.
One ad account across Facebook and Instagram, read in and attributed.
Spend, leads and lead-form submissions are read from your ad account daily; a lead-form or click-to-WhatsApp campaign can be built from here, and everything built is created paused. Qualified leads and won deals are reported back as conversions so the ads bid on customers rather than form fills.
Settings › Ads · More
Search, Performance Max and Demand Gen, with offline conversions.
Campaign spend is read in and matched to the enquiries each ad brought, down to the individual contact. A Google ad that opens WhatsApp carries a reference into the first message, so the conversation knows which ad it came from. Qualified leads and won deals go back through Google's Data Manager API.
Settings › Ads · More
Where new people come from when nobody has written to you yet.
Search and enrich from your own Apollo workspace.
Authorise your Apollo account and search its database from inside Linkubit; a search stores nothing, and an explicit enrich-and-add step writes contacts with their consent basis and source recorded. Every lookup spends your Apollo credits, not ours — Linkubit holds no data of theirs and resells none.
Settings › Integrations
Collecting from your customer inside the conversation, against your own gateway. Linkubit is never in the flow of funds.
Meta's in-chat payment card, on your own gateway configuration.
Choose a payment configuration you have already set up in WhatsApp Manager — Razorpay, PayU, BillDesk or Zaakpay — and a payment request is sent as the order card WhatsApp shows natively. The amount is always a catalogue price; a captured payment closes the deal.
Settings › Payments · More
A payment link from your own Razorpay account, when the card cannot be sent.
Outside the WhatsApp window, on email, or on a number without a payment configuration, the same request goes out as a Razorpay link created against your own key. The link's status is read back from Razorpay until it is paid, and the deal closes at the paid amount.
Settings › Payments · More
How records get in from what you already have, and how what happens here reaches the tools you keep.
Leads and deals on your monday boards, and your team's edits back.
Map a contacts board and a deals board column by column, each with its own direction. Leads land when they are created, qualified or assigned, with a note carrying the conversation summary at each milestone; new items can wait for a person's approval; and a Won status on the board closes the deal here at its value, so revenue and ad attribution follow. A board edit never changes a contact's name, phone or email.
Settings › CRMs · More
Leads, contacts and deals in your Zoho modules, and your team's edits back.
Map Leads, Contacts, Deals, Accounts or a custom module field by field, each with its own direction. Records land when a lead is created, qualified or assigned and when a deal moves, with a note carrying the conversation summary at each milestone; new records can wait for a person's approval; and a Deal reaching Closed Won closes it here at its value, so revenue and ad attribution follow. A Zoho edit never changes a contact's name, phone or email.
Settings › CRMs · More
Every event that matters, signed and delivered to a URL you choose.
Subscribe a URL to lead created, lead qualified, deal opened, won or lost, conversation escalated, campaign replied and the rest. Each delivery is signed with a timestamp inside the signature, retried, and logged attempt by attempt — enough to push into a CRM, a sheet or a Slack channel without waiting for a connector.
Settings › Webhooks
Contacts, companies and products in and out as .xlsx.
Import contacts, companies and leads from a spreadsheet using the templates the product provides, with a consent basis recorded on every row. Export the whole workspace — one JSON file per table — from the settings screen, without a ticket.
Settings › Data · More
The connectors being built next. None has a date; the order is set by who asks, so if one of these is the reason you have not signed up, tell us which and we will say where it is in the queue.
Qualified leads and won opportunities written to Salesforce, with the conversation attached to the record.
Contacts and deals synced to HubSpot, lifecycle stage included.
Your store's catalogue and orders, so the assistant quotes what is in stock and confirms what was bought.
The same for a WordPress store: products in, orders and abandoned carts as conversations.
A sheet that fills as leads qualify, and a sheet that becomes an audience.
The events webhooks already carry, as triggers in Zapier for everything else.
The assistant books a slot on a real calendar rather than proposing a time.
Not yet — outbound webhooks instead. Every event that matters (lead created, lead qualified, deal won, conversation escalated, campaign replied) is signed and delivered to a URL you choose, retried, and logged attempt by attempt. That covers most of what people reach for an API to do, and a read-only API is the next step once somebody asks for it by name.
Today it is one: contacts, companies, leads, a pipeline, scoring and attribution over the same records the conversations write to. Records arrive through the channels, the ad accounts, Apollo and spreadsheet import, leave by export and webhooks, and there is no connector to another CRM yet. Zoho, Salesforce and HubSpot are the ones coming; if your team lives in one of them, tell us which and we will say where it is in the queue.
WhatsApp, email, both payment rails and spreadsheet import are on every plan, including Free. Instagram, Messenger, Meta Ads, Google Ads and Apollo need Pro. Outbound webhooks need Scale. Every new workspace starts with fourteen days of Pro, so the Pro ones can be tried before paying.
Each is a grant in your own name, stored in a managed secrets store, never copied, and revocable from the settings screen or from the provider's side. Apollo calls spend your Apollo credits; a Razorpay link is created against your own key pair; ad spend is billed by Meta and Google to your own accounts. Linkubit is never in the flow of funds and resells nobody's data.
Yes — the planned list is ordered by who asks. Write to us with the tool and what you would want to flow in each direction, and if a webhook already covers it we will say so rather than make you wait.
No coding required. No credit card required.