A mailbox connection can set up a draft. Sending directly after approval is available on a limited basis and requires a separate check for each email.
Please note. Gmail drafts are available in a limited beta. Microsoft 365 and sending after approval have their own availability limits.
The integrations send completed results to a system you choose. Keys and client content belong only in the verified target environment.
Please note. The developer API has its own contract, test environment and release limits. For implementation, use the current download guide and OpenAPI in the Developer API guide.
Options: Drafts · allow sending · correct account
Options: Gmail draft · review · send yourself
Options: Recipient · preview · Bcc · approval · queue
Options: Google · Microsoft · appointments · disconnect
Options: Conversation completed · Report completed · target app · webhook status
Detailed explanation
Connect your own Gmail mailbox and prepare a customer email with suggested attachments as a draft. The Gmail connection is available in a limited beta by invitation from Pro+.
Gmail drafts have been tested in practice. Sending after approval is still undergoing practical testing. Microsoft 365/Outlook is coming soon.
Go to My account → Connections and choose Gmail. To send from Rapportly, also choose Allow sending and complete confirmation. Google bundles creating and sending drafts in the same permission; Rapportly additionally requires your approval for each message.
Open Send directly via Rapportly below your customer email. Enter the recipient and check the preview, including the subject, message, attachments and any Bcc.
Choose Approve and send. If the message or recipient changes after review, you must check a new preview first.
Rapportly puts the approved email in the sending queue. Your sending window determines when it is processed. You can follow its status in Automation.
You can also prepare a draft in Gmail and send it there yourself. Connecting a mailbox does not by itself approve a customer email. Other email providers will follow after their own practical tests.
During the limited beta, Rapportly must first add your Google account to the test group. You then connect it yourself under My account → Connections. You do not need a Google Cloud project, API key or server configuration. Do not share your password with Rapportly.
Choose the Gmail or Google Workspace account you want to send from. It can differ from your Rapportly sign-in address. Check the email address shown after connecting.
Yes. Your organisation may restrict access to connected apps. Ask your Google Workspace administrator to review Rapportly if Google says your organisation has blocked access.
An existing draft connection does not yet have sending permission in Rapportly. Choose Allow sending to enable it. In the current Google testing mode, authorisation expires after seven days and you need to reconnect. You also need to grant permission again after revoking access.
In this workflow, you review the preview and approve each email. Your sending window and any blocks under Automation still apply. Emails wait outside that window. Sent means the email provider has accepted the send request, not that the recipient has read the message.
Go to My account → Connections and choose Disconnect for the mailbox. First check Automation for approved emails that are still waiting. Disconnecting does not delete drafts or sent messages already stored in Gmail.
Zapier can automatically pass a completed conversation summary or report to another system, such as your CRM, spreadsheet or team channel. Zapier is separate from client email: it does not send client email from your Rapportly mailbox.
The Rapportly app in Zapier is available as an invite-only beta from Pro+. You need an invitation to the Zapier app. Only the Rapportly account administrator can create the required API key.
Ask Rapportly for the invitation link and accept it with the Zapier account in which you want to build the automation. Rapportly is not yet listed in the public Zapier App Directory.
In Rapportly, go to My account → Connections. Give the key a recognisable name, such as Zapier CRM, and choose New API key. Copy the key immediately: for security reasons it is shown only once.
Create a new Zap, choose Rapportly as the starting app and paste the API key when Zapier asks you to connect. Do not share the key by email or chat or store it outside Zapier.
Choose Conversation completed to process completed conversation summaries, or Report completed for completed reports. Then choose the destination app and action, such as updating a CRM record or adding a spreadsheet row.
Map only the fields the destination system needs. Preferably test with synthetic data, check the result in the destination app and only then turn on the Zap.
Under My account → Connections, Rapportly shows the active webhook and its latest delivery status. Zapier creates and removes that webhook automatically when you turn the Zap on or off.
You choose the destination system and the data sent to it in Zapier. Check in advance which client data is necessary and who has access. Revoking an API key in Rapportly immediately stops the connected transfer.
The Zapier app is still an invite-only beta and is not publicly listed in the App Directory. First accept Rapportly's invitation link, then check that you are signed in to the correct Zapier account.
No. Only the Rapportly account administrator can create and revoke API keys. The administrator can set up the connection or enter the key directly in Zapier.
That depends on the selected trigger and the fields you map in Zapier. A completed conversation summary or report can contain client data. Send only what is needed and verify that the destination system is covered by your privacy arrangements.
Turn off the Zap so its webhook is removed automatically. To stop access immediately and completely, revoke the corresponding API key under My account → Connections.
Yes. A technical administrator can use the Rapportly API and secure webhooks directly. For a standard CRM, spreadsheet or team-channel connection, Zapier is usually the simplest route.
What you see can depend on your role, your plan and your organisation's integrations. Review every draft you create before you share or send it.