Issues with Zapier pulling event details from Novi for Google Calendar

Hi ​@DenaT 

Help us have more context about what you are referring to by posting screenshots of what you mentioned.

Hey ​@DenaT 👋

Just came across this and wanted to check how you’re getting on—were you able to get this sorted? If so, would you be up for sharing details on how you fixed it? This could be really helpful for others in the Community that having similar issues 🙏

And if it’s still not sending the event details over to Google Calendar, it could be that the fields that were mapped from the webhook don’t contain any values or the wrong fields are selected. 🤔 It’s a bit hard to tell for sure without seeing what’s being sent by the webhook and what’s been selected in the Google Calendar action. To help us get a better idea of can you share some screenshots of the Zap’s setup, as Troy mentioned and we’ll be happy to advise on what might need changing. Make sure to blur/remove any personal info (names, emails etc.) before sharing using a tool like Zappy.

Looking forward to your reply! 

Thanks for you suggestions and patience. I think the issue has to do with Novi AMS This is what Chatgpt said this: Some Novi AMS accounts don’t have every API route enabled by default. Ask Novi support:

"Is the /api/v1/events/{id} endpoint exposed and accessible with a valid API key in our instance?" 

This is what is pulled when the event is created and the event date and time below is when the event was created in Novi, not the actual date and time of when the event is happening.

Event

event.created

Entity Unique Id

2fdb577d-5df2-467c-9e56-5b996ad55a05

Name

Test Event - COPY

Event Date Time

2025-07-28T17:04:08.7684911+00:00

Updated By Role

ASSOCIATION ADMIN

Updated By User

Dena XXXXXX

querystring

Ah, I see! Thanks for sharing those helpful details here, ​@DenaT 🤗

In that case can adjust the permissions for the API Key as ChatGPT suggested?

If you do and that doesn’t fix it, then you’ll need to add an action to search for the event and retrieve it’s full details. I can’t see any “Find Event” action available for the Novi AMA app so I’d recommend reaching out to our Support team to put in a feature request for that sort of action to be added.

In the meantime, you could try using a Webhooks action to make a request to their API to get the event details. It looks like their  GET Event Details endpoint should return both the start and end dates for the event:

If you run into any trouble setting up that Webhooks action let us know, happy to lend a hand if you get stuck!

Hello SamB,

I did try the custom request (get), and it returned an error. This is the setup I have, and here is the error message below. I’d love your help fixing my setup!

The error you're encountering indicates that the request made by the Webhooks by Zapier action is returning a "Forbidden" response (HTTP Status Code: 403). This typically means that there is an issue with the permissions or authentication required to access the API endpoint you are trying to reach. It could also be due to incorrect configuration in the request itself.

How to fix it:

Check API Key/Token: Ensure that the Authorization token you are using is valid and has the necessary permissions to access the endpoint.
Review API Documentation: Double-check the API documentation for any specific requirements regarding authentication, headers, or request format.
Remove Extra Whitespace: Make sure there are no leading or trailing spaces in your headers or URL, especially in the Authorization header.
Test the Endpoint Manually: Use a tool like Postman to manually test the API endpoint with the same parameters to see if you receive the same error.
Verify URL and Method: Ensure that the URL and HTTP method (GET, POST, etc.) you are using are correct and supported by the API.
Check User Permissions: Confirm that the user associated with the API token has the necessary permissions to perform the action you are trying to execute.
​

Sorry to hear you’re running into a 403 error with that custom request, ​@DenaT. Hmm, it looks like the API Key would need to have “Event Data Access” access granted:

Can you take a look in at the settings for the API Key in Novi AMS and confirm it has the correct access?

If the API Key you’re using already has the right permissions then there may be some other issue with the setup of the action. 🤔

In which case, can you share a screenshot of what’s been selected within the Configure section for that Webhooks action? 

That will help us to see the setup of the custom request so we can better identify what might be causing it to error. Be sure to remove any personal info (names, emails etc.) before sharing, using a tool like Zappy. Thanks! 🙂

Hello SamB,

Thanks so much for hanging in there with me. I’m sure it’s the way I’m configuring the Zap. I’m just a beginner:-). Let me know if this helps you at all. I did confirm with Novi that this Zap should be possible.

Here is what Novi folx said: 

Hey Dena,
Thanks for your patience with our back and forth. I think we got ourselves confused internally with some of our own terminology!
I just hopped off a call with one our senior devs and he confirmed this should be possible.
Zapier steps:
1.Event created a trigger to get the ID (you already have this setup)
2.Do a GET Event Details webhook API call, using the event ID - This will give you all details of the event (Here is our API documentation so you can know exactly what fields you'll get and what to look for: https://api-docs.noviams.com/#93d002a0-bb6d-474d-ab7a-f151391a15ee)
3. Create a Google Calendar event!
Again, I'm sorry for that back and forth, I'm glad you kept following up so we could get to the bottom of that!
Once you try that out, let me know if does or doesn't work, either way?

Always happy to help, ​@DenaT! You’re doing great—that setup looks correct based on their API documentation. 🙌 

Only thing I’d suggest is to select False for that Data Pass-Through setting:

 
It could be that for some reason it’s not actually defaulting to false like it should and instead is attempting to pass over the data from the trigger, which might be what’s causing the 403 error. 🤔

Can you give that a try then test that Custom Request action again to see if it then is able to go through successfully?

Hello SamB,

I made the update you suggested but still no luck: the error returned reads:

What this error means:
The error you're encountering indicates that the request made by the Webhooks by Zapier step is returning a "Forbidden" response (HTTP Status Code: 403). This typically means that the API endpoint you are trying to access is rejecting the request due to insufficient permissions or incorrect authentication details.

How to fix it:

1. Check API Key/Token: Ensure that the Authorization token (Bearer token) you are using is correct and has not expired. You may need to generate a new token from the API provider.
2. Review Permissions: Verify that the API key or token has the necessary permissions to access the endpoint you are trying to reach. Consult the API documentation for required scopes or permissions.
3. Remove Whitespace: Check for any leading or trailing whitespace in your headers or URL that might be causing issues.
4. Test the URL: Manually test the URL in a tool like Postman or cURL to see if you receive the same error. This can help isolate whether the issue is with Zapier or the API itself.
5. Consult API Documentation: Double-check the API documentation to ensure that you are using the correct method (GET, POST, etc.) and that all required headers and parameters are included in your request.

SamB,

1. I didn’t create a new token. Should I do that?
2. I don’t how to check the permissions other than the screen shot I sent you before that says “Scope- provide access”
3. I checked for whitespace.
4. When I tested the URL it didn’t pull the event page. But that is probably bc it’s not an active page. It’s just a test event. I did activate it and retest the webhook and still and error. But I feel like this is my problem..somehow the URL is not formatted correctly.
5. I believe you checked the documentation and we are good here.

Thanks for giving that a try ​@DenaT, I’m sorry it didn’t work as hoped. 

1. I didn’t create a new token. Should I do that?

Yes, it may be worth creating a new API Key so you can be sure it definitely has the correct Event Data access.

2. I don’t how to check the permissions other than the screen shot I sent you before that says “Scope- provide access”

I’m not super familiar with Novi AMS, their Support team would be better able to help confirm that the access scopes are correct.

4. When I tested the URL it didn’t pull the event page. But that is probably bc it’s not an active page. It’s just a test event. I did activate it and retest the webhook and still and error. But I feel like this is my problem..somehow the URL is not formatted correctly.

The URL should be the API endpoint not the URL for the event itself. From your the screenshots most of the URL was missing but you had the Entity’s Unique ID being supplied so it appeared to be correct. But just to confirm, the URL should be in this format {{url}}/api/events/eventId:

The {{url}} part would need to be changed to the URL for your Novi website. And the eventId would be the ID for the event that you’re want to get the details of (passed from the Webhooks trigger). 

I believe you checked the documentation and we are good here.

Actually, I had a closer look at their API documentation here and it looks like instead of the usual “Bearer” in the Authorization header, they use the word “Basic”:

Sorry for missing that previously!

Can you try changing Bearer to Basic instead to see if that fixes it:

Keep me posted on how it goes, want to make sure this gets sorted! 

Hello SamB,

I believe I made the adjustments and got past the error.

But when I get to the google calendar step..there is no data to map for the start date and time and end date and time.

I’m so sorry for the delay in my reply, ​@DenaT. Glad to hear using Basic instead of Bearer helped get past the error at least 🙂

Hmm, those 4 fields don’t match the fields that should be returned by Novi’s API. If you try the action again but use a different event ID does that produce the same results or are you then able to access the event data?

If it’s the same four fields again then I’d suggest reaching back out to Novi to have them investigate why they’re not providing the event data. Let me know what they find, curious to know why the full list of fields listed in the example response on their API documentation isn’t coming through to the Zap. 

YAY!!! That’s fantastic news, ​@DenaT! 🎉🎉🎉 I’m so pleased you were able to get it working by switching from a Custom to a GET action event instead. 🙌

If you run into any trouble on your next Zap, or want to share details of what you’ve built, please do reach back out. Until then, happy Zapping! 😁⚡