Hi ​@jawz302,

Thanks for sharing the details. A 404 error usually means Zapier is able to connect to Atera, but the specific endpoint being called in the trigger cannot be found. Since the API key is valid and the connection test works, Here are a few things you can check (as suggested by GPT):

1. Trigger setup – Make sure the selected Atera trigger is supported and that the account has data available for it (e.g., if testing “New Ticket,” there should be at least one existing ticket in Atera).

2. API permissions – Confirm the API key being used has the right permissions for the trigger you’re testing.

3. Endpoint availability – Sometimes Atera changes or restricts endpoints; it’s worth checking Atera’s API documentation to ensure the trigger endpoint exists and is enabled.

4. Zapier app version – Confirm you’re using the latest Atera app in Zapier, as older versions may cause unexpected errors.

If you’ve confirmed all the above and still get a 404, it may be an issue on Atera’s side rather than Zapier. In that case, I’d recommend reaching out to Atera support with the exact trigger you’re testing so they can confirm endpoint availability.

Hey ​@jawz302,

Can you post screenshots of Data In and Data Out as well as how each Zap step is configured for us to have more context?

Here is a helpful article about fixing 404 not found error in Zaps- https://help.zapier.com/hc/en-us/articles/8496215423501-Fix-Not-found-errors-in-Zaps

Referencing some of the fixes from the article-

• Check if the record exists in your app
• Check your custom value or search criteria
• Add a delay step

Hope it helps!

Hi there ​@jawz302, just checking in - did the suggestions from Ashar Malik Easyaiz and Sparsh help to get that 404 error fixed? 

Let us know whether you still need any help, want to make sure this gets sorted! 🙂