Integrations
The systems you can connect to Heqtic yourself, and exactly what is transferred to them. This page is updated on an ongoing basis as the service develops.
The terms for the integrations are set out in the customer agreement § 6 and apply regardless of what this page says — the page describes how we do something the agreement already permits, and cannot expand it. A change to the principle, not just the detail, is an amendment to the agreement under § 12, and you will hear from us.
Last updated:
CRM
Supported today: HubSpot, Pipedrive, Salesforce, Lime CRM, and Upsales. An account can have one of them connected at a time. You connect your own account using credentials you issue yourself and can revoke at any time — for most, an API token; for Salesforce, a Consumer Key/Secret plus your My Domain URL; for Lime CRM, an API key generated by one of your Lime administrators plus your instance URL. Nothing is sent before you do this.
What is transferred
- The company — name, company registration number when we have it, website, and sector.
- The contact person — name, title, and the contact routes the RBS contains (email, phone number, LinkedIn profile).
- The buying signal and analysis — the signal, the sales analysis (why the company fits, angle, and objections), its date, and the sources, as a note on the deal (for Salesforce: in the deal's description field, for technical reasons — same content).
- The entire RBS as a PDF — on the first transfer of an RBS — attached to the deal and the contact, for HubSpot, Pipedrive, and Salesforce. In HubSpot it is uploaded as a private file attached to the note, not to the public file library. The file contains the same material you see with us, including contact details — it must be deleted together with the contact record (customer agreement § 6). Lime CRM and Upsales do not yet support PDF attachment — the RBS still reaches you, just not as a file in the CRM.
Duplicate check
Pipedrive and Salesforce. Before a transfer, we search your account for an existing organisation/Account (by company name) and person/Contact (by email address) to avoid creating duplicates. Only the matched record's ID is stored with us. In Pipedrive, the search means the address appears in Pipedrive's own request logs, at the provider you have your own agreement with.
For HubSpot, Lime CRM, and Upsales, no such search takes place — every transfer of a new company/contact creates a new record the first time; renewed transfers of the same RBS update the same record already created with us.
Automatic transfer on delivery
Under Settings → Integrations, any of your users can turn on having every RBS transferred automatically as soon as it is delivered. Off from the start. Any user can turn it off, and it is reset if you disconnect or change CRM.
With it turned on, your CRM receives a copy of every delivered contact, even ones nobody at your end gets to work on — which expands your deletion obligation under customer agreement § 6. Contacts who have requested not to be processed are never transferred, regardless of setting.
Automatic status update
Optional and off by default, for HubSpot, Pipedrive, Salesforce, and Upsales. When turned on, we check once per day whether deals we ourselves created have been marked won or lost, and store the answer on the corresponding RBS so we can follow up on the quality of what we have delivered. Not supported for Lime CRM — Lime CRM's won/lost status is uniquely configured per account in a way we cannot read automatically for an arbitrary account, so the feature is not offered there at all.
For Pipedrive only, you can additionally, under the same heading, choose which of your own pipeline stages means "Contacted" (e.g. a dedicated column for deals you have reached out to). If you choose a stage, at the same daily check we read whether the deal is in that stage, and mark the corresponding RBS as contacted in Heqtic. The choice is off ("Don't read") until you choose a stage yourself, and cannot be the same stage you have chosen for where new deals are created.
For this feature, we only retrieve the outcome value — and for Pipedrive, if you have chosen a stage as above, which of the two stages the deal is in. No other deals, no contacts, notes, activities, email, or other fields — and a status you have set manually is never overwritten. That limitation is set out in customer agreement § 6 and applies even if this page were to say something else. (The next section describes the OTHER feature that reads your CRM.)
Exclude companies you already work with
Optional and off by default, for HubSpot, Pipedrive, Salesforce, Lime CRM, and Upsales. When turned on, we read, ahead of every delivery, the names of your established organisation/company records in the CRM — to avoid proposing such a company as a new prospect. Any of your users can turn the feature on or off, and it is reset if you disconnect or change CRM.
We read only the names of established company/ organisation records — never contact persons, deal values, notes, activities, or a specific deal's own name, not even for an ongoing deal (this is a deliberate limitation, not a technical one — see customer agreement § 6). The names are never stored with us: they are read at each delivery, included in the material sent to our AI vendor during that specific generation (see the sub-processor page), and otherwise discarded immediately after use — and are never shared with any other customer. If the read cannot be completed (e.g. a transient error or timeout), the delivery proceeds anyway, without waiting for it.
When we withdraw an RBS
If we remove an RBS — for example because someone in it has requested deletion — we remove the deal we created in your CRM and notify you. We cannot reach the note, the attached PDF, or the contact record itself: you must remove those yourself. A deletion on our side does not reach into your system.
Slack
You can connect your own Slack channel using a webhook you issue yourself. We send a notification when new RBSes are ready, and when a person in an already delivered RBS has requested deletion or objected (customer agreement § 5).
- The notification contains RBS metadata — company name and RBS ID — and a link to the deliverable with us.
- If the notification concerns a single RBS, a download link to the RBS as a PDF is also attached. The link has no fixed expiry, but is guaranteed to stop working no later than when the RBS is withdrawn, when we have entered an objection or deletion request into the suppression list, or when the contact details age out of the material (normally 12 months after delivery) — whichever happens first. It contains the entire material including contact details and can be opened by anyone who can see the channel, without logging in with us, for as long as it remains valid — regardless of whether the person was added to the channel after the notification was sent, since the link has no fixed expiry. Choose a private channel accordingly, and clear out old notifications regularly. The notification remains until you remove it, even after the link has stopped working.
- Link preview is disabled, so Slack does not fetch the content to render a preview.
Slack has two roles at once, and they should not be confused: the channel is yours and you are responsible for what remains in it, but the delivery of the notification itself goes through Slack's infrastructure on our behalf. That is why Slack is also listed as a sub-processor on the sub-processor page.
Email notification
You can turn on an email to the account's own account owner, sent when new RBSes are approved. Optional and off by default. If several RBSes are approved in the same batch, a separate email is sent per company, not one combined email.
- Each email lists the company name concerned and a link to the deliverable with us, plus (since 2026-10-11) a short sentence about which type of buying signal is involved — drawn from a small, pre-defined list of categories, never from the free-form research text, and never figures, dates, or any person's name. See the customer agreement § 6.
- Each email also attaches a download link to that specific RBS as a PDF — the same kind of link, on the same terms, as the Slack notification's PDF link above: no fixed expiry, but guaranteed to stop working no later than when the RBS is withdrawn, when we have entered an objection or deletion request into the suppression list, or when the contact details age out of the material (normally 12 months after delivery) — whichever happens first.
- The email is sent via our vendor Resend and is therefore listed as a sub-processor on the sub-processor page, the same role Slack has for its own notification.
RBS webhook
You can connect your own webhook — a URL you specify yourself, against a system you control yourself, e.g. your own HighLevel/ FunnelBud integration. The feature is optional and off by default. For security reasons, we today only accept a URL of the form https://services.leadconnectorhq.com/…; other hosts are rejected. On each delivery, we post each RBS as structured JSON to the URL.
- The content is the same as the CRM transfer above: company name, domain, sector, contact details, buying signal, analysis, and sources — plus, when one is stored, the entire RBS as a PDF, base64-encoded directly in the call (no subsequent fetch is needed to access the file).
- The call also contains a link to the same PDF, for anyone who opens your own record later. The link requires no login with us and is guaranteed to stop working no later than when the RBS is withdrawn, when we have entered an objection or deletion request into the suppression list (customer agreement § 5 — which can take up to the 5 business days § 5 allows from when the objection reaches us), or when the contact details age out of the material (customer agreement § 8, normally 12 months after delivery) — whichever happens first. If we rotate the underlying signing key in response to an incident, every link stops working at once, regardless of age — that is deliberately our fastest available block.
- Before you receive a real delivery, you can send yourself a sample call to your URL, with made-up data (company name, contact person, etc. are clearly marked as examples), so you can build your field mapping in advance.
The recipient is your system, not a sub-processor of Heqtic — we have no account and no access at FunnelBud/HighLevel beyond the URL you have provided, the same way as for the CRM above. Their infrastructure (LeadConnector) is US-hosted — that is your own recipient's region, not a transfer Heqtic makes, the same way the region choice for your CRM below is your own.
Where the data ends up
Which region your CRM stores data in is determined by your own account and is your responsibility. HubSpot is hosted in the US (DPF + SCC, EU data hosting optional); Pipedrive is EU-based (Estonia), but your account may be set to a US region; Salesforce depends entirely on which instance your organisation has (choose an EU instance in your own Salesforce configuration if needed); Lime CRM and Upsales are both Swedish companies and normally host within the EU. Regardless of vendor, the region choice is your own account's, not something Heqtic controls.
Once the data has been transferred, you are the independent controller for the processing there. See the customer agreement § 6 and the sub-processor page.