Integrations
Your proposals in your tools.
A CRM that’s up to date is a CRM nobody re-types. Through its API and webhooks, Cuevr passes every moment of the proposal, from creation to signature, to the scenario you configure.
14 days · 5 proposals · no credit card
Your CRM
Maison BérylAnnual renewal
- Proposal
- SentSigned
- Total incl. VAT
- €11,016
- Last event
proposal.signed
Updated by your scenario
SMSophie MartinFinance director · Maison BérylSigned
Sent to your CRMproposal.signedproposal.signed
What is a CRM integration for sales proposals?
Definition
A CRM integration connects the software where you write your sales proposals to the one where you track your deals, so each knows what happens in the other without entering data twice. In Cuevr, it works through an API, which lets your tools read and create clients and proposals, and through webhooks, which send each moment of the proposal to the address you specify.
Every moment of the proposal, in your CRM.
Cuevr sends the facts; you decide where they go and what they trigger.
Fourteen events, from creation to signature
Created, published, opened, read in depth, signed, declined: Cuevr sends an event at every moment of the proposal. You pick the ones that matter, and your CRM knows what just happened. The signature and the deal outcome remain two separate events.
proposal.viewed · proposal.signed · proposal.outcome_changed
Integrations in detailAn address, a test, a delivery log
A connection that fails silently is one you discover at the worst moment. Cuevr tests the destination before it goes live and signs every delivery, which your tool verifies. The log keeps each delivery for 30 days; if your tool doesn’t respond, Cuevr retries, then disables the destination after repeated errors.
HTTPS · HMAC-SHA256 · cuevr.ping
Delivery logA proposal created from your CRM
The deal starts in the CRM, not in an editor. Through the API, your CRM or your scenario creates the proposal in Cuevr from the deal, with the notes at the top of the file, in their original language. If the creation is replayed, it doesn’t create a duplicate, thanks to the external source and ID.
proposals:write · clients:write · qualification:read
In CuevrSame file, no duplicate
The quote amount, the same everywhere
Does your CRM show the amount your prospect reads? With Cuevr, it does: the quote follows the same calculation in the editor, on the published page and in the data sent to your integrations, so your CRM receives the amount your prospect reads. A cost that can’t be read as an amount is excluded and flagged, never guessed.
Subtotal · Discount · Total excl. VAT · VAT · Total incl. VAT
The quote in detail- option€1,800
Start with the proposal, connect your tools next.
Try Cuevr on a real deal; integrations are then set up in your organization’s admin area.
There’s more to Cuevr
Deal qualification
Learn moreYour meeting notes become a qualified deal, with what’s missing and the questions to ask.
Editor and Cuevr AI
Learn moreOn-brand proposals with sales-ready blocks, written by Cuevr AI.
RFP responses
Learn moreThe response framework drawn from the buyer’s documents, and every requirement checked before submission.
Interactive proposals
Learn moreA clear page on desktop or phone, always on the latest published version.
E-signature
Learn moreYour prospect accepts the proposal where they read it, with a simple, legally binding electronic signature.
Proposal tracking
Learn moreInvite your readers by email: each one is named, and you see what they read, section by section.
Templates and teams
Learn moreShared templates, reusable components and sharing subject to approval, for the whole team.
Frequently asked questions
Does Cuevr connect to our CRM?
Yes, through its API and webhooks. Cuevr sends an event at every moment of the proposal, from creation to signature, and your CRM can create a proposal from a deal. You connect it directly or through a tool like Make or n8n, depending on the scenario you configure.
Does Cuevr have a native HubSpot or Salesforce connector?
No: Cuevr doesn’t offer a ready-made connector for any one CRM. The link goes through the API and webhooks, directly if your CRM can call an API and receive a webhook, or through an automation tool like Make or n8n, depending on the scenario you configure.
Which events does Cuevr send by webhook?
Fourteen. On the proposal side: created, published, sent, reshared, opened, read in depth, signature form opened, signed, declined, deal outcome recorded or lifted. Around it: qualification completed, sent only once, and a client created or modified. For each destination, you keep the ones your scenario needs.
Can we be notified when the prospect reads the proposal?
Yes, by webhook, and you set the noise level: Cuevr doesn’t send an email at every read, the signals stay in Cuevr. To be alerted elsewhere, you forward the opened or read-in-depth events to the tool of your choice, which sends the message or creates the task you planned.
Can we create a Cuevr proposal from our CRM?
Yes, through the API: your CRM or your scenario creates the proposal from a deal, the notes arrive as they are at the top of the file and the language is kept. If the scenario replays the creation, the external source and ID prevent a second file. Condition: the owner’s email must match a member of your organization.
Does a signed proposal mark the deal as won in the CRM?
Not by itself. The signature and the commercial outcome are two separate events: proposal.signed on one side, proposal.outcome_changed on the other, when the deal outcome is recorded. Your scenario decides what each one changes in your CRM.
Are Cuevr webhooks secure and reliable?
Yes: destination addresses are HTTPS and every delivery carries an HMAC-SHA256 signature that your tool verifies. A delivery only counts as delivered on a 2xx response in under 10 seconds; otherwise, Cuevr retries at increasing intervals, then disables the destination after repeated errors. The delivery log is kept for 30 days.
Who can set up integrations?
The organization’s owner and administrators. They create the keys, each with its own permissions, and up to 10 webhook destinations. A key’s secret is shown only once, and an unused key can be revoked. If the subscription becomes inactive, access switches to read-only, but you can still revoke a key or disable a destination.
Your proposals move forward, and your CRM knows.
Try Cuevr on a real deal, then connect it to your tools with an API key and a webhook destination.
From the key to the first event.
Create a key
Your flow only gets the permissions it needs, and the key’s secret is shown just once.
Add a destination
The HTTPS address of your scenario or your tool, and the events that matter to you.
Test
A test event leaves Cuevr and your tool verifies the signature: you know it holds before the first real deal.
Enable
Events go out to your tool and the delivery log shows what arrived.
Let your scenario act
The scenario updates the deal in your CRM, alerts the team or creates a proposal in Cuevr, depending on what you configure.