Resources · Make integration

MyCalendarAlerts Make integrationAutomate MyCalendarAlerts with Make.

Can a calendar alert start an automation on its own? The MyCalendarAlerts Make integration gives you 1 scheduled trigger that picks up event alert notifications. This guide shows how to link your account, build a first scenario and test it before you switch it on.

Try the MyCalendarAlerts integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MyCalendarAlerts Make integration let you automate?

The MyCalendarAlerts Make integration links your MyCalendarAlerts account to Make so that event alert notifications can start a scenario, which is the automation you build in Make as a chain of modules. It offers one module only, a trigger, so everything that happens after the alert comes from another app you add next.

Tell the team in chat. Put Watch Event Alert Notification first, then add a messaging app after it. Each alert that Make picks up becomes a bundle, one item passed from a module to the next, and the chat module posts it where your colleagues already look.

Keep a written trace of every alert. A spreadsheet or database module placed after the trigger can add one row per alert, which gives an office manager a record to check later instead of a pile of notifications.

Hand the alert to a task tool. If alerts mean work to do, a project tool can receive them as new tasks. The trigger is the same in all three cases; only the second module changes.

Know the limits before you start. Make itself says its documentation for MyCalendarAlerts is limited because little public information exists about the app, so the fields the trigger returns are only visible once you test it. Our Make troubleshooting page helps when a first run returns nothing. MyCalendarAlerts may also have a node in n8n; the n8n vs Make comparison lays out how the two tools differ, and the Make pricing guide explains what a scenario costs in operations.

Connect

How do you connect MyCalendarAlerts to Make?

  1. 01

    Add the trigger and open the connection

    In a new scenario, search for MyCalendarAlerts, pick Watch Event Alert Notification and click Create a connection. A connection is your MyCalendarAlerts account linked to Make once, then reused by the module.

  2. 02

    Give the connection a clear name

    Naming it is optional, but a label such as the account owner or the calendar it covers saves guesswork later, when several people share the same Make organization and pick from a list.

  3. 03

    Authorize and save

    Either sign in on the MyCalendarAlerts page that opens and approve access for Make, or paste the key the app gives you, depending on what the window asks for. Then click Save to finish.

First scenario

Your first scenario with MyCalendarAlerts

GoalWhen MyCalendarAlerts produces an event alert notification, Make picks it up and passes it to the app of your choice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to place the first module.

  2. 02

    Place the MyCalendarAlerts trigger

    Type MyCalendarAlerts in the search, choose Watch Event Alert Notification and select the connection you created, or click Create a connection if you have not yet.

  3. 03

    Add where the alert should go

    Click the + on the right of the trigger and pick the next module from another app, such as a chat or a sheet. Map the alert data from the trigger into its fields.

  4. 04

    Test with Run once

    Click Run once and look at the bundles the trigger received. Since the docs do not list the returned fields, this test is the only way to see what an alert contains.

  5. 05

    Schedule and switch it on

    Open the clock on the trigger. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Save, then switch the scenario on.

Triggers

What starts a MyCalendarAlerts scenario

1 module starts a scenario when something happens in MyCalendarAlerts. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MyCalendarAlerts as soon as it happens.

MyCalendarAlerts1Watch Event Alert Notification

Watch Event Alert Notification

triggerIn the docs only

This trigger turns the event alert notifications of your MyCalendarAlerts account into bundles, so a reminder can travel on to any app you place after it. It is the only door into MyCalendarAlerts from Make.

How it fires
scheduled. Make checks the app on the scenario's schedule, which is shown by the clock badge; the type is inferred from the module name, as the docs give no description.
When to use it
whenever an alert should create something elsewhere, a message, a row or a task.
Watch out
run it once before mapping anything, because the fields it returns are not documented.
Need help

Need help automating MyCalendarAlerts with Make?

A person reads every message.

FAQ

MyCalendarAlerts and Make: common questions

01Is the MyCalendarAlerts Make integration free?
Yes, on Make's side. MyCalendarAlerts is a standard app, so it works from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in operations each month. Whatever MyCalendarAlerts charges for its own service is outside the scope of this page.
02What do you need to connect MyCalendarAlerts to Make?
A MyCalendarAlerts account and a Make account are the starting point. The documentation lists no other prerequisite and no dedicated steps, so the generic Make flow applies: add the trigger, click Create a connection, optionally name it, then either approve access on the MyCalendarAlerts page or paste the key the app provides, and click Save. If the window asks for a setting you cannot find, look in your MyCalendarAlerts account, because the docs do not cover it.
03Does the MyCalendarAlerts trigger fire instantly?
No. Watch Event Alert Notification is treated as a scheduled trigger, a type inferred from its name since the docs describe nothing else. Make asks MyCalendarAlerts for new alerts at each scheduled run, every 15 minutes by default. On the Free plan 15 minutes is also the shortest gap, while paid plans can go down to 1 minute. An alert is therefore handled at the next check, not the moment it appears, which matters if the reminder is close to the event itself.
04What if the MyCalendarAlerts module you need is missing?
It depends on what you need. The app offers a single trigger and no Make an API Call module, so Make cannot create, change or look up anything inside MyCalendarAlerts. Anything that should happen after the alert has to be done by another app in the same scenario. If the calendar itself needs to change, check whether the calendar tool behind your alerts has its own Make app. For a setup that stays stuck, the team can review the scenario with you.
05Should you use Make or n8n for MyCalendarAlerts?
It depends on the tool your team already runs. MyCalendarAlerts may have an n8n node as well, so compare the two on what you would build: here, one alert trigger followed by modules of other apps. In Make the path is short, with a scheduled trigger that is available from the Free plan and a connection created from the module itself. This page does not rank them; the n8n vs Make comparison linked above walks through the differences.
Same platform

Other docs you might need on this stack.

Browse all integrations