Source: https://www.revvly.ai/docs/reference/integrations Reference # Integrations and *availability* What connects to Revvly today, what has limits, and what does not exist yet. Checked against the product in October 2026. ## How to read the status - **Live**: You can use it now with no help from Revvly. - **Live with limits**: It works, with the boundaries named in the row. - **Needs set-up by Revvly**: It depends on a key or setting only Revvly can configure. Ask us to switch it on. - **Not available yet**: It does not exist in the product. Work in progress or on a plan is not counted. ## Google One Google consent screen covers Drive, Gmail and Calendar. The permissions listed here are what each one is actually used for. - **Google Drive import Live with limits**: 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. - **Google Drive client folders Needs set-up by Revvly**: 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](https://www.revvly.ai/docs/guides/drive-folders). - **Gmail (mailbox) Live with limits**: 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. - **Google Calendar Not available yet**: 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. ## Workspace tools - **Slack Live with limits**: 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. - **ClickUp (OAuth connection) Live with limits**: 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. - **Calendly Live**: 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. - **Intercom and Zendesk help centres Live with limits**: 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. - **Forms embed Live**: Published forms are served as a hosted page and as an embeddable script. See the [Forms guide](https://www.revvly.ai/docs/guides/forms). ## APIs and automation - **Zapier and Make Live with limits**: 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. - **MCP for Claude Live**: 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](https://www.revvly.ai/docs/api/mcp). - **Public GraphQL API Live**: API-key access to clients, subscriptions, invoices and payment summaries, with a growing set of writes. See [Public GraphQL API](https://www.revvly.ai/docs/api/graphql-public). - **REST usage and events API Live**: Report metered usage and stream signed events. See [Event Ingestion API](https://www.revvly.ai/docs/api/events) and the [usage reporting guide](https://www.revvly.ai/docs/guides/usage-reporting). - **Payment webhook (inbound) Live**: Your payment system posts invoice payment status into Revvly. See [Invoice Payment Webhook](https://www.revvly.ai/docs/api/invoice-payments). ## Platform - **Email sending Live**: 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. - **Sign-in and SSO Not available yet**: 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. - **Installable app and push Needs set-up by Revvly**: 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). ## Payments, accounting and other mail - **Stripe Live with limits**: 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. - **QuickBooks and Xero Not available yet**: Planned. Nothing is built, so no accounting push or sync exists today. - **Outlook and Microsoft mail Not available yet**: Not supported. Mail sync, sending and drafts work with Gmail only. Meeting invites that arrive as calendar attachments are still read from Gmail. ## Support: what exists Revvly Support needs the Support module turned on for your workspace. Setup steps are in the [Support setup guide](https://www.revvly.ai/docs/guides/support-setup). - **Tickets and inbox Live**: Tickets with public replies and internal notes, assignment, status workflows, attachments that are scanned before use, and notifications by email and in the app. - **Knowledge base Live**: 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. - **AI first line Live with limits**: 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. - **ClickUp work items Live with limits**: Link or create ClickUp tasks from a ticket, with client-facing stages. See the ClickUp row above for limits. - **Ticket webhooks Live**: Send ticket.created, ticket.message, ticket.status_changed, ticket.updated, ticket.closed, ticket.reopened and ticket.progressed to your own endpoint. - **Chat API for your own widget Live**: Your server mints an end-user token and your front end talks to the Support chat API. See [Build a Support widget](https://www.revvly.ai/docs/guides/support-widget) and the [Support chat API](https://www.revvly.ai/docs/api/support-chat). ## Support: what is not part of it today - **SLAs Not available yet**: No response or resolution targets, timers or breach alerts. - **Macros and canned replies Not available yet**: No saved replies. Agents write each reply. - **Automation triggers Not available yet**: No rules that act when a ticket changes. A status workflow only defines which statuses exist and which moves are allowed. - **Routing and round-robin Not available yet**: Tickets are assigned by a person. The only routing setting picks a default ClickUp list for each ticket type. - **An email channel Not available yet**: Revvly sends Support notification emails, but a customer cannot open or answer a ticket by emailing a support address. - **A packaged chat widget Not available yet**: There is no drop-in widget. You build the chat front end on the chat API.