where to find emails in DevRev interface after email integration
ART-2027_KNOWLEDGE_NODE-26
configuration instructions, refer to [Email snap-in configuration](/docs/integrations/email-config).\n\nFor more information, refer to the [Email snap-in](/marketplace/email-with-tickets) on the DevRev marketplace.\n\nConversation and ticket creation for emails\n-------------------------------------------\n\nWhen an email is received, DevRev checks if the sender is linked to your workspace and creates a conversation or ticket. If a sender is not recognized, DevRev creates a new user profile to
Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-49
select **Forward all emails sent to this mailbox**, enter the forwarding address v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai, and choose whether you want to keep a copy of forwarded emails. If you don\'t see this option, make sure a license is assigned to the user account. Select **Save changes**.\n\nOnce added, an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-47
**Primary Use Case** is **Tickets**, go to **Support** > **Tickets** in the DevRev app; otherwise, if the **Primary Use Case** is **Conversation** go to **Inbox**. Find and open your verification message here.\n6. Open the given link to confirm the request. Make sure you click the link that allows your support address to be forwarded to v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai.\n7. Go back to your Gmail forwarding settings, select **Forward a copy of incoming mail** and **Save
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-51
an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be rendered correctly as HTML, making the invite button inaccessible directly. To accept the invitation, you\'ll need to download the email.eml attachment and open it in your preferred mail client. From there, you can click **Accept invite**.\n\nZoho Mail\n\nTo enable forwarding, add the
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-39
Notifications**.\n\n* Each notification type\xe2\x80\x94such as being assigned, mentioned, or when a customer esponds\xe2\x80\x94can be toggled for both in-app and email delivery.\n\n### The email composer in Tickets\n\nInside every ticket, under the **Customer Messages** tab, agents can access a fully featured email composer. This allows direct email communication with customers from within DevRev.\n\nHere\xe2\x80\x99s what the email component supports:\n\n| Feature | Icon / Access Point |
Email | Integrate | Snap-ins | DevRev
ART-3207_KNOWLEDGE_NODE-52
v\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_@hooks.devrev.ai address as a member in your Zoho Mail group. Once added, an invitation is sent to the hooks address.\n\nThe invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be rendered correctly as HTML, making the invite button inaccessible directly. To accept the invitation, you\'ll need to download the email.eml attachment and open it in your preferred mail client. From there, you
Email snap-in configuration | Email | Integrate | Snap-ins | DevRev
ART-16082_KNOWLEDGE_NODE-27
Connection**.  \n   In the connection modal, click **Sign in with snap-in** (with the Gmail\n   icon), enter a connection name, and proceed to **authorize via your Google\n   account using OAuth**.  \n   Provide the necessary permissions and click **Continue** to complete the\n   setup.\n5. Once the connection is established, select the email labels/folders you want\n   to import and specify the DevRev part where imported emails should reside.\n   This starts the bulk import.\n\nDevRev attempts
Gmail AirSync | AirSync | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-37
If Channel is not email, it is sent from the email address configured in the snap-in under **Notification sender email address**.   - If no email snap-in is installed, the reply is sent from [notifications@devrev.ai](mailto:notifications@devrev.ai). | Yes |\n| Replies to notification emails | Email reply | Response added to ticket thread | Yes |\n\n![]()\n\nEven when a reply comes via email, it\xe2\x80\x99s always synced into the customer\xe2\x80\x99s portal view.\n\nEmail experience from an
Email | Integrate | Snap-ins | DevRev
ART-16082_KNOWLEDGE_NODE-25
capabilities.\n\nSupported objects\n-----------------\n\nThe following is a list of Gmail objects and their corresponding DevRev\nequivalents. Those marked as Sync to DevRev are eligible for import from Gmail\nto DevRev.\n\n| **Gmail Object** | **DevRev Object** | **Sync to DevRev** |\n| --- | --- | --- |\n| Attachments | Attachments | \xe2\x9c\x85 |\n| Labels | Tags | \xe2\x9c\x85 |\n| Users | Identities | \xe2\x9c\x85 |\n| Threads | Chats | \xe2\x9c\x85 |\n| Customers | Customers |
Gmail AirSync | AirSync | Snap-ins | DevRev
ART-2027_KNOWLEDGE_NODE-28
email address that messages to it create either a conversation or a ticket, but not both simultaneously. Whether to create a conversation or a ticket depends on the nature of the emails received at a specific email address.\n\nRead more about [conversations](../product/conversation) and [tickets](../product/tickets) to decide which is more suitable for your use case.\n\nWhen needed, you can link a conversation to a ticket. This is particularly useful if you decide to use conversations for all
Email | Integrate | Snap-ins | DevRev