MyCalendarAlerts® is not a replacement for your calendar. Instead, it works with your existing calendars and adds powerful alerting, messaging, and automation capabilities.

You create reusable Alert Policies that describe when an action should occur. MyCalendarAlerts applies those policies to your calendar events and can then notify contacts or trigger remote automations.

Some of the things you can do with MyCalendarAlerts include:

• Create reusable Alert Policies that automatically apply to many calendar events.
• Send notifications to contacts by email, supported messaging services, and MyCalendarAlerts app notifications.
• Subscribe different contacts to different Alert Policies.
• Receive notifications when important calendar events are approaching.
• Send calendar summaries and group messages.
• Trigger Webhooks or RPCs when an Alert Policy fires.
• Connect calendar activity to automation platforms such as Zapier® and Make®.

MyCalendarAlerts can be useful for both business and personal calendars.

• Monitor rental calendars and receive notifications about guest arrivals, departures, cleaning schedules, and other turnover activities.
• Track appointments for businesses such as healthcare, consulting, coaching, tax preparation, personal services, and other scheduled activities.
• Monitor work calendars and receive reminders for meetings, deadlines, and other important events.
• Notify employees, contractors, cleaners, maintenance personnel, or other service providers about calendar events relevant to them.
• Trigger Webhooks or RPCs to update databases, websites, or other business systems.
• Use integration platforms such as Zapier® and Make® to connect calendar activity with other applications.

• Receive additional reminders for appointments and important events.
• Maintain birthday and anniversary calendars and notify family members.
• Receive advance reminders for holidays or recurring events.
• Share selected reminders with friends, family, clubs, or other groups.
• Send calendar summaries and group messages to your contacts.

MyCalendarAlerts works with supported online calendars that can be connected directly or provide an iCalendar/ICS calendar feed.

MyCalendarAlerts offers several subscription plans so you can choose the amount of calendar, contact, alerting, group, and automation capacity that fits your needs.

The Free plan can be used without purchasing a paid subscription. Paid plans increase available capacity and provide additional features.

Prices shown above are the current standard U.S. monthly prices. Actual billing may vary by provider, currency, taxes, promotions, or platform.

Subscription purchase and management options may vary depending on where the subscription was purchased. Existing subscriptions should continue to be managed through their original billing provider.

MyCalendarAlerts is also available as a mobile app.

The mobile app provides access to account information, subscription management, alerts, and other MyCalendarAlerts features from supported mobile devices.

App-store installation links and direct app-opening links will be added here as they are finalized.

A typical MyCalendarAlerts setup consists of the following steps:

1. Create your MyCalendarAlerts account.
2. Configure one or more calendars and your time zone.
3. Create Alert Policies that describe when alerts or automations should occur.
4. Add contacts who should receive alerts.
5. Subscribe each contact to the appropriate Alert Policies.
6. Optionally configure Remote APIs for Webhooks, RPCs, or other automations.

Account Configuration contains settings that apply to your MyCalendarAlerts account, including calendar connections, time zone, messaging options, and alerting behavior.

Your calendars must be connected to MyCalendarAlerts before their events can be monitored.

Depending on the calendar provider, this may be done through a direct calendar connection or by providing an iCalendar/ICS calendar URL.

Instructions for obtaining an ICS calendar URL vary by calendar provider. See the dedicated Calendar Sync URL help page for more information.

When using an ICS URL:

• The URL should point to a valid iCalendar feed.
• If you open or download the file manually, it should contain standard iCalendar data such as BEGIN:VCALENDAR.
• MyCalendarAlerts periodically checks connected calendars for updates.
• Calendar changes may cause scheduled alerts to be regenerated.

Setting the correct time zone is important because it determines when scheduled alerts are interpreted and delivered.

See the Time Zone help page for additional information.

MyCalendarAlerts supports multiple notification methods. Available methods depend on your account configuration, contact configuration, subscription plan, and the messaging services you choose to use.

Contacts can be configured individually for supported messaging options such as:

• Email
• MyCalendarAlerts app notifications
• Supported SMS or third-party messaging services
• No SMS service when SMS messaging is not required

For details about available messaging options and how account-level and contact-level settings interact, see:

Understanding Chat and SMS Messaging Configuration

MyCalendarAlerts includes test options that can help verify messaging configuration before you depend on it for scheduled alerts.

When a test button is available on an Account Configuration or Contact form, save your changes before running the test. The test uses the saved configuration rather than unsaved values currently displayed in the form.

Contact-level tests are useful for confirming that the selected messaging method and recipient information are configured correctly.

MyCalendarAlerts can send email alerts using the supported account email configuration.

If you configure your own email account, your email provider may require an application-specific password rather than your normal login password.

Consult your email provider's instructions for SMTP configuration and application-password requirements.

Event inclusion and exclusion keywords can be used to control which calendar events are processed by your alerting rules.

These filters can also be configured on individual Alert Policies when more specific behavior is needed.

Account Configuration also includes global Remote API fields for Webhooks and RPCs.

These global fields are intended for remote actions that should apply broadly across the account rather than only to selected Alert Policies.

For more selective automation, create reusable Remote APIs in the Remote APIs Manager and link them to individual Alert Policies.

See the Remote API help section below for more details.

Pause Monitoring temporarily stops MyCalendarAlerts monitoring and alert processing for the account.

Alert Policies are reusable rules that determine when MyCalendarAlerts should take action for calendar events.

A policy can result in one or more actions, including:

• Sending notifications to subscribed contacts.
• Triggering Remote APIs.
• Applying event filters so only matching events are processed.

A single Alert Policy can apply automatically to many calendar events. This is one of the major advantages of MyCalendarAlerts: you do not need to manually create the same reminder for every calendar event.

• Notify me on the day a guest arrives.
• Notify me one day before a guest leaves.
• Send an alert a specified number of minutes before a timed appointment.
• Notify a cleaning crew before an upcoming rental turnover.
• Send reminders 10, 5, and 1 days before an event.
• Apply alerts only when an event contains specific keywords.
• Exclude events containing specified keywords.
• Trigger a Remote API when a matching event occurs.

Alert Policies can schedule actions relative to the beginning or end of calendar events.

Relative Timing Around a Calendar Event

Common timing concepts include:

• Before or after the event start.
• Before or after the event end.
• A specified number of days before or after the selected edge.
• Relative minute-based timing for events that contain a specific start or end time.
• A default time of day for all-day events.

A relative day count of zero means the same day as the selected event start or end.

Alert Policies can use inclusion and exclusion keywords to determine whether a calendar event should match the policy.

• Inclusion keywords can require the event to contain specified text.
• Exclusion keywords can prevent matching events from generating alerts or automation actions.

Creating an Alert Policy does not automatically send notifications to every contact.

Contacts must be subscribed to the Alert Policies whose notifications they should receive.

Remote APIs linked directly to a policy can still be triggered when that policy fires, even when no contact notification is required.

Contacts are the people who can receive notifications generated by your Alert Policies.

It is often easiest to create your Alert Policies before adding contacts so that you can immediately subscribe each contact to the policies they need.

Depending on the notification methods you plan to use, a contact may include:

• First and last name.
• Email address.
• Phone number and country code when required for the selected messaging service.
• Messaging-service configuration.
• Notification enable/disable settings.
• Alert Policy subscriptions.
• Calendar-summary notification preferences.

For detailed information about supported messaging options, see:

Understanding Chat and SMS Messaging Configuration

After contacts have been created, the Contacts List can be used to select recipients for group messages.

Available delivery methods depend on each contact's configuration and enabled messaging options.

Open the Contacts List

Contacts can also be configured to receive calendar summaries. Calendar-summary features are useful for sharing upcoming calendar activity with selected recipients.

After your calendar, Alert Policies, and contacts have been configured, review the following pages:

• Upcoming Events
• Alert Policies
• Contacts
• Scheduled Alerts

The Scheduled Alerts page is especially useful for confirming that your policies are producing alerts at the expected times.

1. Select a contact that should receive the test alert.
2. Confirm that the contact's desired notification methods are configured and enabled.
3. Confirm that the contact is subscribed to the Alert Policy you want to test.
4. Temporarily adjust the policy timing so that an alert is scheduled a few minutes into the future.
5. Review Scheduled Alerts and confirm that the expected alert appears.
6. Wait for the scheduled time and confirm that the expected notification is received.
7. Restore the policy to its normal timing after the test.

Additional MyCalendarAlerts information is available through these resources:

• MyCalendarAlerts Introduction
• Account Creation and Setup
• MyCalendarAlerts Facebook Page

MyCalendarAlerts Remote APIs allow calendar alerts to trigger actions on other systems.

Remote APIs can be configured in several different ways depending on whether the automation should apply globally, only to selected Alert Policies, or through an external integration platform.

The Account Configuration page includes fields for configuring global Webhook and RPC endpoints.

A Remote API configured in these global fields is not tied to one specific Alert Policy. It can be triggered broadly as part of the account's alert-processing flow.

Use the global configuration when the same remote action should apply across your account rather than only to selected policies.

Open Account Configuration

Remote APIs can also be created in the Remote APIs Manager and then explicitly linked to individual Alert Policies.

This is useful when a remote action should occur only for certain types of calendar events or only when selected policies fire.

For example, one Alert Policy could trigger a Webhook used for rental arrivals while another policy could trigger a different Webhook for departures.

Some integration platforms can create or subscribe to Webhooks as part of their own setup process.

For example, an integration configured through Zapier may create the required subscription or Webhook connection through the integration platform rather than requiring you to manually enter the endpoint in the MyCalendarAlerts Remote APIs Manager.

Other platforms, such as Make, may provide a Webhook URL that you then configure manually in MyCalendarAlerts.

• Webhooks send HTTP requests to another application or service.
• RPCs trigger supported remote procedures or functions on another system.

A Remote API can be used for activities such as:

• Updating a remote database.
• Starting another business process.
• Sending calendar-event information to another application.
• Triggering automation workflows.
• Reserving, releasing, or updating resources when calendar events occur.

The Remote APIs Manager is used to create and maintain reusable remote API definitions that can be linked to Alert Policies.

Open the Remote APIs Manager

MyCalendarAlerts includes a Remote API testing form that can send sample calendar and alert data to a configured endpoint.

This allows you to verify that the receiving system is reachable and can correctly process the MyCalendarAlerts request before relying on the API for live alert processing.

Open the Remote API Testing Form

When possible, first select the Remote API from the Remote APIs Manager and then use its test option. This can populate the testing form with the saved API configuration and reduce the amount of information you need to enter manually.

The testing form sends representative test data only. Live Remote API calls are generated from actual calendar events and the Alert Policies that triggered them.

Zapier can connect MyCalendarAlerts with other applications and use calendar-driven events as part of automated workflows.

See the Zapier configuration help page for additional information.

Make is another automation platform that can receive Webhooks and connect MyCalendarAlerts activity with other applications and services.

MyCalendarAlerts integrations can use Webhooks supplied by Make as endpoints for calendar-driven automations.

Subscription-management options depend on the billing provider that manages your subscription.

The MyCalendarAlerts Free, Plus, Pro, and Business plans determine the subscription entitlements available to your account.

Existing subscriptions should continue to be managed through their original billing provider.

To cancel a paid subscription, use the subscription-management options provided by the billing provider that manages that subscription.

Cancellation does not necessarily end paid access immediately. Depending on the provider and subscription state, access may remain available through the end of the already-paid subscription period.

When no paid subscription grants access, the account uses the Free plan and its associated entitlements.

Cancelling a MyCalendarAlerts account is separate from cancelling a paid subscription.

If you have an active paid subscription, cancel the subscription through its billing provider before permanently cancelling the MyCalendarAlerts account.

If an account has been cancelled but is still eligible for reactivation, use the available account-reactivation option and review the account configuration after signing in.

Subscription status and available features will depend on the account's current subscription state.

Terms of Service

Review the current MyCalendarAlerts Terms of Service .

If you have a question or need help with MyCalendarAlerts, you can submit a support question here .

You can also visit the MyCalendarAlerts Facebook Page to share feedback, ask questions, or discuss how you use MyCalendarAlerts.