What is your goal?
Basically, I want to try make a Discord to Notion automation using Make, where Make will detect Discord messages, then copy it, and paste it in Notion as a task in a database.
What is the problem?
Unlike the other way around where Notion tasks can be automated through Make, then Make sending the notifications of database changes (i.e. stasus, deadline, etc), I can’t make it so the Integromat bot copies the messages and send it to Notion, as in the Notion side, it will just return empty.
What have you tried so far?
I tried reading the apps documentation for Discord (Discord - Apps Documentation), but I am still quite confused on how the “Discord - Apps Documentation” thing works, especially with the new Discord bot update. Also, it seems that the redirect URL’s are broken, as I can’t invite my bot to the Discord server, and I’m quite confused on what integration type I should use. If anyone can help, it will be greatly appreciated! Thanks!
Create public scenario page
Screenshots: scenario setup, module configuration, errors
More than anything it looks like you are encountering a Discord developer issue and not an issue with Make.
What you have is two separate Discord flows. The redirect URI(make.com / integromat.com) is used just for Make’s OAuth connection to be able to read your server, but does not invite the bot. In order to actually invite the bot you will have to go to your app’s Installation page within the Discord Developer Portal to switch the Integration Type to “Guild Install”. You will then need to set the install link to “Discord Provided Link” and add the permissions and bot scope you need. Use that generated URL to invite it. Then once the bot’s in the server you should be able to connect your Watch Messages module to your Notion “Create a Database Item” module.
In addition the “empty in Notion” issue is usually just a mapping problem and not something with the connection. Double check that you are mapping the message Content field into a Notion property that is actually a text/rich text type of field. The most common reason it is blank is mapping the wrong field type.
the key detail here is to separate authentication from the message pipeline. for a first test, create the Discord bot in the Developer Portal, invite it with the bot scope and only the permissions it needs, such as View Channel and Read Message History. the OAuth2 redirect URL is for an OAuth connection, not for the bot invite itself. in Make, run the Discord trigger once and send a fresh message in a channel the bot can read. map the message content field to a Notion database page title or rich_text field instead of mapping the whole bundle, and store the Discord message id as an external key to avoid duplicates. if the first bundle is empty, check the Message Content intent and channel permissions, then run the trigger again. that should narrow the issue to authentication, event capture, or Notion mapping.
