New Airtable Record to Discord Message - Status Code 404

Help
, ,
1

Hi,
I am trying to develop a workflow that send a Discord message to a specific channel upon a New record event in our Airtable database. I have connected both Discord and Airtable, I have given the Pipedream bot a specific role that allows it to enter the channel in Discord. However, when I test the workflow in Pipedream, I am getting the “Request failed with status code 404” in the second step of the process (sending the Discord message).
The details look like this:

    at null.createError (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/createError.js:16:15)
    at null.settle (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/adapters/http.js:269:11)
    at IncomingMessage.emit (events.js:412:35)
    at null.endReadableNT (internal/streams/readable.js:1333:12)
    at process.processTicksAndRejections (internal/process/task_queues.js:82:21)

I am not familiar with the language, so if anyone has any info on how to resolve this, please let me know. Thanks!

2

Hi @antoniovachev

First off, welcome to the Pipedream community. Happy to have you!

A 404 error means that whichever record you are attempting to access or update in the API is missing or doesn’t exist.

Please refer to the API’s documentation and the error message in the response from the API for more details to narrow down which part of the payload is missing or is referencing the wrong record.

3

Hi Pierce,
I feel like that can’t be it. I create a new record, which I then select manually so I am sure it is in the database.
Why would I be able to see the record in the trigger and not be able to send a message from it?

image
image1164×702 32.1 KB

4

Hi @antoniovachev

I believe you mentioned the 404 is happening during the Discord Send Message action.

That means that the configuration of the step is most likely the issue.

Double check your props on that step and make sure that guild/channel still exists and that your Discord connection has sufficient privileges to interact with that server.