Integrations
Proposal events, where your team already works.
When a proposal is sent, opened, accepted or declined, Declario can tell Slack, HubSpot or your own system. This page lists what works today and what doesn't yet.
Available now
Each of these works end to end today. Plan requirements are checked on the server.
Slack
- What it is for
- Post proposal activity to a Slack channel so the team sees it without opening Declario.
- How it connects
- Incoming webhookCreate an incoming webhook in Slack and paste its URL into Declario. It is not a Slack app and does not use OAuth. Messages go to the one channel that webhook belongs to — one channel per workspace, with no per-event channel mapping.
- Events
- proposal.sent
- proposal.viewed
- proposal.accepted
- proposal.rejected
- client.created
- approval.requested
- approval.approved
You choose which of these events are posted.
- Where to set it up
- Settings → Integrations, by pasting the webhook URL.
Webhooks
- What it is for
- Send proposal events to your own system as JSON over HTTPS — a CRM, a data warehouse or an internal tool.
- How it connects
- Signed HTTPSAdd an endpoint URL and choose its events. Declario sends a signed POST request to that URL when an event happens.
- Events
- proposal.sent
- proposal.viewed
- proposal.accepted
- proposal.rejected
- client.created
- approval.requested
- approval.approved
Each endpoint subscribes to its own selection of these events.
- Request signing
- Every request carries
X-Declario-Signature:t=<unix ms>,v1=<hex hmac>, andX-Declario-Eventwith the event name. The signature isHMAC-SHA256over<t>.<raw request body>, keyed with the endpoint secret, which is shown once when you create the endpoint. - Not yet
- There are no automatic retries and no delivery log yet. If your endpoint is down or times out, that delivery is not repeated.
Any tool that can receive a webhook can consume these events, including Zapier's generic webhook trigger. There is no native Zapier app.
- Where to set it up
- Settings → Integrations, under Webhooks.
HubSpot
- What it is for
- Keep HubSpot contacts and deals in step with your clients and proposals, without typing them in twice.
- How it connects
- OAuthConnect your HubSpot account with OAuth. Declario asks for read and write access to contacts and deals only.
- What it does
- When you create a client, creates or updates the matching HubSpot contact (found by email), with name and company.
- When you send a proposal, creates a deal with the proposal title and value in the default pipeline, linked to the client's contact. One deal per proposal.
- When that proposal is viewed, accepted or declined, updates the deal's stage — accepted moves it to closed won, declined to closed lost.
- When a client declines with a reason, adds the reason to the deal as a note.
- Where to set it up
- Settings → Integrations, with Connect HubSpot.
- What it is for
- Sign in to Declario with a Google account instead of a password.
- How it connects
- OAuthGoogle OAuth, used for sign-in only. Declario does not read your Gmail, Calendar or Drive.
- Where to set it up
- On the sign-in and sign-up pages.
Not available yet
None of these can be connected today. We list them so you know what we are considering, not as a promise of dates.
- PipedriveComing soonA CRM connection for Pipedrive is planned.
- Google CalendarComing soonA Google Calendar connection is planned.
- Microsoft TeamsComing soonNotifications in Microsoft Teams are planned.
- REST APIComing soonA public REST API is planned. Signed webhooks are the way to get proposal data out today.
Need an integration that isn't here? Tell us what you would connect
For developers
Build on proposal events
The documentation describes how to set up a webhook endpoint and check its signature. There is no public API yet.
APIComing soon