Integrations and availability

You can use it now with no help from Revvly.

It works, with the boundaries named in the row.

It depends on a key or setting only Revvly can configure. Ask us to switch it on.

It does not exist in the product. Work in progress or on a plan is not counted.

Uses read access (the drive.readonly scope). You pick folders to sync; Revvly reads PDF, JPEG and PNG files and extracts invoice data for review before anything is committed. The import itself writes nothing to Drive; writing is client folders, below, which ask for more access.

Switched on per workspace by Revvly. A Drive folder per client and prospect, under roots you choose: Revvly creates folders and writes invoices, credit notes, uploads and attachments into them, and brings back files your team adds. This needs write access (the drive scope), asked for by Enable client folders. Revvly only writes inside the chosen folders and never deletes, trashes or re-shares anything. See Client folders in Google Drive.

Each user connects their own mailbox. Revvly reads and sends mail and manages drafts (gmail.modify) and imports your signature (gmail.settings.basic). It sits behind the CRM module. A workspace can also connect one shared accounting mailbox for invoice intake. Gmail is the only mailbox provider; see Outlook below.

The consent screen can ask for calendar permission, but nothing in Revvly reads or writes your Google Calendar today. Meetings reach the CRM from Calendly bookings and from calendar invites attached to synced email.

Install the Revvly app into your workspace, map members to Revvly users, and use it for OKR check-ins by direct message, the /revvly command and the conversational bot. Slack can also be used to sign in to an invited account. The app is installed by link and is not listed in the Slack Marketplace.

One connection serves three things: work links on OKR Key Results (refreshed about every 30 minutes), ClickUp Chat as a check-in channel (replies are polled each minute and this path has had less production use), and Support work items. Support can link tasks, create a task from a ticket and add comments to linked tasks. Revvly only adds tasks and comments; it never moves or edits an existing task.

Bookings arrive as CRM meetings and, for new people, as prospects. You connect with a Calendly token under Settings, Booking intake. Revvly does not create bookings in Calendly.

Import a help centre into the Support knowledge base using your own API token. Reads only; nothing is written back. Intercom also supports importing past conversations. A Zendesk conversation import does not exist.

Published forms are served as a hosted page and as an embeddable script. See the Forms guide.

There is no Zapier or Make app to install. You paste a catch-hook URL into an outbound webhook endpoint, signed with a per-endpoint secret. The only events sent today are CRM lead.created, lead.updated and lead.deleted, optionally filtered by pipeline. Support has its own, separate ticket webhooks.

Connect Claude or any MCP client with OAuth or an API key. Reads are live; writes are proposals a signed-in person approves. See Connect Claude with MCP.

API-key access to clients, subscriptions, invoices and payment summaries, with a growing set of writes. See Public GraphQL API.

Report metered usage and stream signed events. See Event Ingestion API and the usage reporting guide.

Your payment system posts invoice payment status into Revvly. See Invoice Payment Webhook.

Invoices, sign-in and invitation emails, and Support notifications are sent by Revvly through Amazon SES. Email you send to a client from the CRM goes out through your own connected Gmail mailbox.

Accounts sign in with email and password, or with Slack for people invited that way. There is no SAML, OIDC or enterprise single sign-on, and no Google sign-in.

The dashboard installs as a PWA. Browser push notifications work only once Revvly has configured the push keys for the environment. Triggers: subscription renewed or churned, invoice paid or overdue, unverified metered usage, a subscription not live after signing, and a shared document opened (sender only).

An admin connects the workspace’s own Stripe account under Settings, Payments. A client’s card is saved through Stripe’s own form (or startPaymentMethodSetup on the public API), so card numbers never reach Revvly, and invoices issued after both the connection and the card exist are charged automatically. Invoices issued before, imports and backfilled history are never charged. A Stripe account can be connected to one workspace only. Card charges can be followed with the payment.* webhooks. Other payments are still recorded through the inbound payment webhook or by hand on the invoice.

Planned. Nothing is built, so no accounting push or sync exists today.

Not supported. Mail sync, sending and drafts work with Gmail only. Meeting invites that arrive as calendar attachments are still read from Gmail.

Tickets with public replies and internal notes, assignment, status workflows, attachments that are scanned before use, and notifications by email and in the app.

Sources are a website crawl, uploads, Intercom or Zendesk help centres, and your own system through the API. Articles can be reviewed by audience before they are used.

Answers from your knowledge base, with a daily spend cap you control. A resolution is billed only when it is recorded as AI resolved. Needs the Support module and the AI provider key configured for the environment.

Link or create ClickUp tasks from a ticket, with client-facing stages. See the ClickUp row above for limits.

Send ticket.created, ticket.message, ticket.status_changed, ticket.updated, ticket.closed, ticket.reopened and ticket.progressed to your own endpoint.

Your server mints an end-user token and your front end talks to the Support chat API. See Build a Support widget and the Support chat API.

No response or resolution targets, timers or breach alerts.

No saved replies. Agents write each reply.

No rules that act when a ticket changes. A status workflow only defines which statuses exist and which moves are allowed.

Tickets are assigned by a person. The only routing setting picks a default ClickUp list for each ticket type.

Revvly sends Support notification emails, but a customer cannot open or answer a ticket by emailing a support address.

There is no drop-in widget. You build the chat front end on the chat API.