Skip to content
Notis

Connect Mapulus to Planyo Online Booking

When something happens in Mapulus, Notis takes the next step in Planyo Online Booking. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Mapulus to Planyo Online Booking

View example

Check booking availability for a mapped location

Send a location and proposed dates from a Mapulus workflow to Notis, then check whether its Planyo resource is available before you reply or make plans.

View example

Check dates for a nearby mapped resource

When a Mapulus-based enquiry identifies a nearby Planyo resource, check its availability for the requested dates through Notis.

View example

Check blackouts for a mapped resource

Before suggesting a mapped place, ask Notis to check Planyo blackout periods for its relevant resource and the dates under consideration.

View example

Create a reservation from a mapped-place enquiry

When a location enquiry arrives through your Notis webhook with confirmed resource, timing, and customer details, create its Planyo reservation.

View example

Add a Planyo user from a mapped enquiry

When a Mapulus-driven enquiry provides the details needed for a new customer profile, use Notis to add that user in Planyo.

View example

Run a daily availability scan for mapped places

On a daily schedule, have Notis check Planyo availability for the mapped resources and date ranges you specify in its instruction.

View example

Review mapped-resource blackouts each week

Have Notis check weekly blackout periods for the Planyo resources linked to places you are planning around in Mapulus.

View example

Fetch reviews for a mapped resource

When a location is under consideration, use a Notis webhook to retrieve Planyo reviews for its identified resource.

View example

Inspect add-ons for a mapped resource

For a location being considered, use Notis to retrieve the add-ons available for its identified Planyo resource.

Supported Triggers and Actions

Notis builds workflows that link Mapulus to Planyo Online Booking. A trigger fires from one place; an action lands in another.

Mapulus triggers

Planyo Online Booking actions

Recurring trigger

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

TriggerScheduled

Add Reservation

Tool to create a new reservation. Use after gathering resource, timing, and customer details.

ActionInstant

Webhook trigger

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

TriggerInstant

Add User

Tool to add a new user in Planyo. Use when you need to create a user account after gathering user details.

ActionInstant

Get Add-on List

Tool to retrieve a list of add-ons. Use when you need to inspect or manage add-ons for a specific resource or across the entire site after setting up credentials.

ActionInstant

Get Coupon List

Tool to retrieve a list of coupons. Use when you need to fetch all coupons for a specific resource or the entire site (if no resource_id provided).

ActionInstant

Get Resource Availability

Tool to check resource availability within a specified date/time range. Use when validating if a resource can be reserved before creating a reservation.

ActionInstant

Get Resource Blackouts

Tool to fetch blackout periods for a resource. Use when determining unavailable timeslots before booking.

ActionInstant

Get Resource Reviews

Tool to fetch reviews and ratings for a specific resource. Use when you have a resource_id and need to display customer feedback.

ActionInstant
Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only
Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match
Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

Notis

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect Mapulus and Planyo Online Booking

Connect any two apps with Notis in the middle.

Mapulus and Planyo Online Booking, 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 Planyo Online Booking.