Connect Discord and Request Tracker (RT) to unlock the power of automation
- No credit card required
- Free forever for core features
- 14-day trial for premium features and apps
How Zapier works
Zapier makes it easy to integrate Discord with Request Tracker (RT) - no code necessary. See how you can get setup in minutes.
Choose a trigger
A trigger is the event that starts your Zap—like a "New Message Posted to Channel" from Discord.
Add your action
An action happens after the trigger—such as "Comment on a Ticket" in Request Tracker (RT).
You’re connected!
Zapier seamlessly connects Discord and Request Tracker (RT), automating your workflow.
Supported triggers and actions
Zapier helps you create workflows that connect your apps to automate repetitive tasks. A trigger is an event that starts a workflow, and an action is an event a Zap performs.
- ChannelRequired
Try ItTriggerPolling- Channel typeRequired
- Emoji
- Limitation_notice
Try ItTriggerPolling- Forum Channel
- Ignore previously archived Posts?Required
Try ItTriggerPolling- Role Assigned to User
Triggers when a role is assigned to a user.
Try ItTriggerPolling
- New User Added
Triggers when a new user joins the Discord Server.
Try ItTriggerPolling - Forum ChannelRequired
Try ItTriggerPolling- Channel typeRequired
- Member
Try ItTriggerPolling- UserRequired
- RoleRequired
ActionWrite
Zapier is the automation platform of choice for 87% of Forbes Cloud 100 companies in 2023




93%
Customers who say using Zapier has made them better at their job
25m
Customers have created over 25 million Zaps on the platform
6 mins
The average user takes less than 6 minutes to set up a Zap
Learn how to automate Discord on the Zapier blog
Frequently Asked Questions about Discord + Request Tracker (RT) integrations
New to automation with Zapier? You're not alone. Here are some answers to common questions about how Zapier works with Discord and Request Tracker (RT)
How do I set up an integration between Discord and Request Tracker?
You can set up an integration between Discord and Request Tracker through Zapier by creating a Zap. This involves choosing Discord as your trigger app, selecting an event like 'New Message Posted to Channel', and then choosing Request Tracker as the action app, where you might create or update a ticket.
What triggers are available for Discord in the integration with RT?
We offer various triggers for Discord such as 'New Message Posted to Channel', 'New Reaction Added', and 'User Joins Guild'. These triggers allow you to initiate different actions in Request Tracker, like creating tickets or appending messages.
Can I automatically create tickets in RT from Discord messages?
Yes, by setting up a Zap where the trigger is 'New Message Posted to Channel' on Discord, you can configure the action to create a new ticket in Request Tracker automatically.
What actions are supported within RT when using the integration with Discord?
In our integration setup, Request Tracker supports actions such as creating new tickets or updating existing tickets. You can trigger these actions from events on Discord like posting new messages.
Is it possible to update an RT ticket when there’s new activity on a specific Discord channel?
Certainly. When you define your Zap with a trigger like 'New Message Posted to Channel' in Discord, you can specify actions that will update corresponding tickets in Request Tracker with details from the message.
How do I handle different types of information from Discord in RT?
During the integration setup, you can map fields from your Discord triggers to corresponding fields in Request Tracker. This allows for organized information transfer such as assigning message content to ticket descriptions or matching user info.
Are there any limitations I should be aware of when integrating Discord with RT?
While our integration supports key features like ticket creation and updates, complex workflows may need custom scripting within your environment for full functionality. It's important to test setups thoroughly.