Setting up re:amaze as a Source
Connecting re:amaze makes it easy to bring your support conversations and customer insights directly into Guru. Your team can search, reference, and learn from past support interactions without switching toolsβmaking every conversation a knowledge-building opportunity.
Access RequiredGuru Access: You need to be an Admin, Source Creator, or relevant custom role to set up Sources.
re:amaze Access: The authenticating user must have Admin or Staff access to the re:amaze account. API access is available on all re:amaze plans.
Setting up re:amaze as a Source
- In Guru, go to Manage.
- Select Sources, then click Add Source.
- Choose re:amaze from the list of integrations.
- Authenticate using your re:amaze account credentials.
- Enter your re:amaze subdomain (e.g., if your re:amaze URL is
yourcompany.reamaze.com
, enteryourcompany
). - Provide your re:amaze API key:
- In re:amaze, go to Settings > API.
- Copy your API key or generate a new one if needed.
- Filter data to start pulling content in from a specific start date (optional).
- Add a display name for the Source (optional) and click Connect Source.
- Assign which Guru Groups should have access to this content.
The sync will begin immediately. Depending on the volume of conversations, the initial sync may take several hours to complete.
NoteThe status will change from "Initializing" to "Synced" once the initial sync is complete. You can continue using Guru while the sync runs in the background.
What gets synced from re:amaze
Conversations | Messages | Staff Info | Customer Info | Metadata | Web URLs |
---|---|---|---|---|---|
Conversation threads | Full message content | Staff names | Customer names | Status (resolved/unresolved) | Deep links to conversations |
Conversation subjects | Timestamps | Staff roles | Customer emails | Tags | re:amaze-generated URLs |
Channel info (email, chat, social) | Message formatting | Assignee details | Customer companies | Priority levels | Attachment links |
Tipre:amaze conversations are synced with their full thread history, making it easy to understand the complete context of customer interactions when searching in Guru.
Managing your re:amaze Source
Once connected, your re:amaze Source will automatically sync new and updated conversations. You can manage sync settings and access permissions at any time.
To update sync settings:
- Go to Manage > Sources.
- Find your re:amaze Source and select Settings.
- Adjust your sync preferences:
- Update the start date to sync older or newer conversations
- Modify Group access permissions
- Pause or resume syncing
- Click Save Changes.
To disconnect re:amaze:
- Go to Manage > Sources.
- Find your re:amaze Source and select Settings.
- Click Disconnect Source.
- Confirm the disconnection.
ImportantDisconnecting a Source removes it from search results and AI features. Previously synced content will no longer be accessible through Guru.
Frequently asked questions about re:amaze
How often does re:amaze sync with Guru?
re:amaze syncs continuously in real-time. New conversations and updates typically appear in Guru within a few minutes.
Can I filter which conversations get synced?
Currently, all conversations from the specified start date forward are synced. You can control access to this content by assigning specific Guru Groups to the Source.
What happens to resolved conversations?
All conversations are synced regardless of status. This ensures your team can learn from past resolutions and customer interactions.
Are attachments from re:amaze conversations synced?
Links to attachments are included in synced conversations. Users can click through to view attachments in re:amaze directly.
Will syncing re:amaze affect my API rate limits?
Guru's sync process is designed to respect re:amaze's API rate limits. The initial sync may take longer for accounts with extensive conversation histories, but it won't impact your daily operations.
Can I sync multiple re:amaze accounts?
Yes, you can connect multiple re:amaze accounts as separate Sources. Each Source can have different Group access permissions.
Updated about 3 hours ago