
How to Set Up Auto-Forwarding from Gmail to Revdoku's Email
Table of Contents
- Before you start
- What changes when you forward email
- 1. Open Gmail’s settings
- 2. Find the forwarding settings
- 3. Add a forwarding address
- 4. Enter the support address
- 5. Confirm the destination
- 6. Close the notice
- 7. Open the confirmation email in Revdoku
- 8. Confirm forwarding with Google
- 9. Return to Gmail
- 10. Create a recipient filter
- 11. Choose the forwarding action
- 12. Test the filter and the ticket
- Forward every new email instead
- Troubleshooting
- Before you start
- What changes when you forward email
- 1. Open Gmail’s settings
- 2. Find the forwarding settings
- 3. Add a forwarding address
- 4. Enter the support address
- 5. Confirm the destination
- 6. Close the notice
- 7. Open the confirmation email in Revdoku
- 8. Confirm forwarding with Google
- 9. Return to Gmail
- 10. Create a recipient filter
- 11. Choose the forwarding action
- 12. Test the filter and the ticket
- Forward every new email instead
- Troubleshooting
Forward email from Gmail or Google Workspace to the support address of a Revdoku docs site. Each forwarded email then opens a support ticket (#N) in the bucket of the docs site. A bucket holds one docs site, its files and its support tickets. Use this setup when customers already write to an address in Gmail, for example support@yourcompany.com.
The screenshots show a filter that forwards only email sent To one address. To forward every new email that is not spam, use the section “Forward every new email instead” after step 12.
Google Workspace accounts with a custom domain use the same Gmail settings. The screenshots show this type of account.
Before you start
Use a computer and a browser.
- In Revdoku, open the bucket of your docs site.
- Open Support, then open Email Settings (the cog at the top right).
- On the Email address tab, copy the support address.
The address ends in @revdokumail.com, unless the bucket receives email on your own domain. This tutorial uses <name>@revdokumail.com as a placeholder.
What changes when you forward email
Gmail keeps the original sender in the From line of each forwarded email. Revdoku makes that sender the requester of the ticket. Later email in the same conversation joins the same ticket.
Revdoku sends only replies, and only to a requester whose email passed SPF or DMARC. SPF and DMARC are checks that a domain really sent an email. A forwarded email comes from the servers of Google, so SPF cannot prove the original sender. Revdoku can reply only when the domain of the original sender passes DMARC on the forwarded copy. If it does not pass, the ticket shows the email, but nobody can reply to it from Revdoku. In that case, reply from Gmail.
A reply from Revdoku comes from the support address, not from your Gmail address. When the customer answers that reply, the answer goes to the support address and joins the ticket.
The built-in support agent drafts replies from your docs, and a person reviews and sends each draft. The support agent does not answer junk or automatic mail. For a forwarded email, it drafts a reply only when Revdoku can reply to the requester.
If you turn on Receive only from in Email Settings, add the original senders or their domains. Do not add your Gmail address, because the forwarded email keeps the original From line.
1. Open Gmail’s settings
In Gmail, click the Settings gear in the upper-right corner. Then click See all settings to open the full settings page.

2. Find the forwarding settings
Open the Forwarding and POP/IMAP tab.

3. Add a forwarding address
In the Forwarding section, click Add a forwarding address.

4. Enter the support address
Paste the support address that you copied from Revdoku. In this tutorial, it is <name>@revdokumail.com. Make sure that you copied the complete address, then click Next.

5. Confirm the destination
Google opens a confirmation window. Make sure that the address is the support address of your docs site. Then click Proceed.

6. Close the notice
Gmail sends a confirmation link to the support address. Click OK.
Gmail does not forward email yet. First, open the confirmation email in Revdoku and accept the request.

7. Open the confirmation email in Revdoku
The confirmation email from forwarding-noreply@google.com arrives as a new ticket in Support.
- In Revdoku, open the bucket of your docs site.
- Open Support.
- Open the ticket from
forwarding-noreply@google.com. - Click the confirmation link in the email.
Use the link from your own confirmation email. If the ticket is not in Inbox, open the Junk folder. The AI filter checks each new email and puts phishing and prompt injection in Junk.
8. Confirm forwarding with Google
Google opens a confirmation page with two addresses. Make sure that the first address is your Gmail or Google Workspace address. Make sure that the second address is the support address.
Click Confirm.

9. Return to Gmail
Confirmation Success! means that Google accepted the support address as a forwarding address. Gmail still forwards no email: the filter in steps 10 and 11 starts the forwarding.
Return to Gmail. If the settings page is open, refresh it.

10. Create a recipient filter
Open Show search options in the Gmail search bar. In To, enter the Gmail or Google Workspace address that receives your customer email. Do not enter the support address. Leave the other fields empty, then click Create filter.
The screenshot uses a source address on a custom domain. This filter forwards only new email sent To that address. It can miss email to aliases, Bcc copies and mailing lists.
A reply is forwarded only when it also matches the filter, as Google’s filter documentation explains.

11. Choose the forwarding action
Select Forward it to and choose the support address. Click Create filter to save the filter.
The screenshot also shows Mark as read. You do not need this option. Leave it clear to keep the email unread in Gmail. Do not change the delete, archive and spam options, unless you want those actions.
Gmail does not forward old email, also when you apply the filter to matching conversations. The filter forwards only new email that matches it.

12. Test the filter and the ticket
- Open Settings > Filters and Blocked Addresses.
- Make sure that the filter shows the correct To address and the Forward to action.
- Make sure that the Forward to address is the support address.
- From a different email account, send a new test email to your Gmail address. Attach a small file.
- In Revdoku, open Support and make sure that a new ticket shows the email and its attachment.
- Reply to the test ticket from Revdoku. If Revdoku cannot reply, read the section “What changes when you forward email”.

Forward every new email instead
Gmail can also forward every new email that is not spam. This method also forwards email that does not match the To filter. Use it only for a Gmail address that receives support email, because every new email becomes a ticket.
After Google accepts the support address:
- Open Settings > Forwarding and POP/IMAP.
- Select Forward a copy of incoming mail to and choose the support address.
- Select keep Gmail’s copy in the Inbox.
- Click Save Changes.
For more information, read Google’s automatic forwarding instructions.
Use only one forwarding method for the support address. If you change to this method, delete the filter of step 10 in Filters and Blocked Addresses.
Troubleshooting
- If the confirmation email is not in Revdoku, make sure that Gmail has the complete support address. Then open the Junk folder in Support.
- If the support address is not in the Gmail list, complete step 8 and refresh Gmail.
- If no email arrives, send a new email that matches the filter. Gmail does not forward old email.
- If Gmail shows no forwarding option, ask your Google Workspace administrator. An administrator can turn off automatic forwarding for users.
- If Revdoku cannot reply to a forwarded email, the domain of the original sender did not pass DMARC. Reply from Gmail.
Code and AI apps read the same tickets with the tickets API, the Revdoku CLI or Revdoku MCP.
A docs portal with Ask AI
and support tickets
Connect a repository, or describe your product to start. Each docs site has search, Ask AI, an API console, an MCP server and support tickets.
- Publishes from GitHub on every push
- Works with Mintlify repositories
- API console from your OpenAPI file
- MCP server and llms.txt for AI agents
- Ask AI and support tickets
- Analytics for people and AI agents
