Skip to content
Notis

Give important signature requests a time slot

Send a request with its signing deadline and the time you want to reserve. Notis adds the hold to your calendar.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Create Event

Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.

Why this helps

Signature requests can sit in an inbox until the deadline is suddenly close, leaving no time to review or sign.

  • Reserve time before a signing deadline
  • Keep signing work visible alongside other commitments
  • Reduce last-minute searches for the request

Setup

Build it in a few focused steps.

  • 1Connect Boloforms and Google Calendar once in the Notis portal.
  • 2Create an automation from any channel or in Automations, New Automation.
  • 3Tell Notis to create a calendar block for each signing request using the deadline and requested reservation time in the webhook.
  • 4Pick notis_webhook as the trigger and choose where run reports go.
  • 5Test with one real request that includes a deadline and reservation time.

Questions about this workflow

Does this trigger automatically when Boloforms creates a request?

Boloforms has no listed trigger event here. This workflow starts when the configured Notis webhook receives a request payload.

What information should the webhook include?

Include the signing deadline and the desired calendar hold start and end times. Notis needs usable times to create an event.

Can Notis guess how long the signing will take?

The event needs start and end times. Supply the reservation window in the webhook or include it in your instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Boloforms to Google Calendar. A trigger fires from one place; an action lands in another.

Boloforms triggers

Google Calendar actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Insert Calendar into List

Inserts an existing calendar into the user's calendar list.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Update Calendar List Entry

Updates an existing entry on the user\'s calendar list.

ActionInstant

Delete Calendar

Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.

ActionInstant

Update Calendar

Updates metadata for a calendar.

ActionInstant

Clear Calendar

Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.

ActionInstant

Create Event

Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.

ActionInstant

Delete event

Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.

ActionInstant

Create a calendar

Creates a new, empty google calendar with the specified title (summary).

ActionInstant

Connect any two apps with Notis in the middle.

Boloforms and Google Calendar, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Google Calendar.