This topic was automatically generated from Slack. You can find the original thread here.
Is the Postmark trigger down or having a bug? I’ve created my Postmark account with account and server keys. Simple copy paste. But creating a trigger in a new workflow, I’m getting a AxiosError. I see 401 unauthorized. So, just want to see if there is any one else having this error.
Hi Tim, which trigger are you trying to set up?
There are technically two different types of Postmark API keys from what I understand.
If you’re using an Account key, perhaps try a Server key instead or vice versa
Hi Pierce.
I’m creating a Postmark New Inbound Received Trigger.
Here is what the creating the account/connection looks like. It is asking for both the account and the server of which I put in both.
Got it. Could you try entering in your credentials one more time? You can see your Postmark account under the Accounts section in the Pipedream dashboard.
Just want to make sure they weren’t swapped by accident when they were entered in
Certainly, I understand. I did it twice before for this reason. Let me go ahead again and see that all lines up. Will report back
Ah ok. Just a thought. It might not the problem and might actually be a bug or perhaps the API key doesn’t have permission. But I don’t think Postmark has individual permissions on keys
Recreated, and absolutely confident I have the right key in the right Pipedream input.
These are coming up when I’m trying to “create source” when creating the trigger.
Doesn’t hurt to check. Maybe the component code itself might be referencing the wrong token.
You’re welcome to clone the repository for this trigger and modify it if you’d like. Or you can open a bug report on the repository for a component dev to take a look
I’ll look at bug report. Though typically I don’t mind diving in and helping, this week is a bit chaotic.
Thank you for your guidance.
Of course, also I just wanted to let you know I think a new version was released recently:
I’m going to double check if this fixes the issue
A dev replied on my bug ticket and Postmark Inbound Email is working.
At least I got one email through, right now Postmark is having trouble hitting the webhook, but that may be the email I sent in or a postmark thing.
my point is the problem I experienced yesterday I believe to be resolved.
Awesome, glad to hear that
