I’ve created a (public) configuration and successfully then created bookings (against Google Calendar). All good, this works fine.
But is it possible using the POST to book an event to give it a unique description and location? I’ve tried putting in a description string field and it’s ignored.
I’m assuming it’s just using the settings from the configuration ID.
Since this is public configuration and anyone could hit the API I assume it’s there to stop people sending abusive/random descriptions etc?
Is this supported if it was a private configuration? We have a scenario where we are connecting a voice agent to someone’s calendar and the reason for the meeting and the location can vary each time.
Yes, I could create a configuration element for each unique meeting but seems a bit excessive and brute force. I’d then have to remember to clear them up. But I’m assuming this is the only way?
Additionally the calendar entries show up as tentative (outlined) in Google Calendar, even tho thats not the mode I’ve used… there doesn’t appear to be any way to force them into the calendar as fully accepted meetings… (full colour, not outline)
Hello @chris Here’s some comments from the Scheduler team
For their use case they can create public configuration with additional fields under Booking form tab in the scheduler Editor. They can add the additional fields that they want to capture. This way, the end user booking the event can fill in the information they want to capture.
Ok thanks. I had trouble getting the demo editor working (from Github etc, on Mac/Safari) so I just ended up testing with the POSTMAN apis so I can give this a try.
But do these fields map into the event that is saved over on Google Calendar under location and description ….?
I’ve implemented this approach, which works; however, when updating the Calendar Event immediately after the booking is created, the participants will receive an “Updated invitation:” email which is particularly annoying.
I don’t believe there is a way to silence these emails…
Ideally, it would be nice if the book an event endpoint supported event specific parameters that would overwrite the configuration’s like Title, Description, and Location so that we can have more control of the created Calendar Event from the booking.
I don’t think this is a Nylas bug, I think it’s a limitation based on your current endpoints / internal implementation.
For the Update an event endpoint, there is no request parameter to update the event silently. Every time I use this endpoint to update an event, the participants get an email that the event was updated. It would be nice if a request parameter could be added to the nylas endpoint that allows us to control these update emails. I looked into the Google calendar api and it looks like it’s a query parameter, so it should be doable fairly easily.
Adding this to the current Nylas Update Event endpoint would be a great enhancement and prove to be a suitable workaround for the original issue.
Ultimately, it would be nice to add new functionality to the Book an event endpoint that allows us to supply request parameters to override the configuration’s defaults for things like title, description, location, etc… so that we don’t have to bother updating events like this. (The current title and description request parameters don’t override the created calendar event’s title and description, it looks like they’re only saved to the intermediary NylasBooking)
