Put new client details where scheduling happens
Move useful intake details into Calendarhero so the next scheduling step starts with a contact record.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Contact
Tool to create a new contact. use after confirming contact details before making the api call.
Why this helps
New client information can arrive in forms or internal tools and still need manual re-entry before scheduling.
- Reduce manual re-entry from intake sources
- Keep client details ready for scheduling
- Make contact creation consistent
Setup
Build it in a few focused steps.
- 1Connect the intake source and Calendarhero once in the Notis portal.
- 2Create an automation for webhook contact intake.
- 3Tell Notis to create a contact from confirmed details and report any missing required information.
- 4Choose a webhook trigger and a report channel.
- 5Send one real example HTTP request and verify the resulting contact.
Questions about this workflow
Can this work with any intake tool?
It can start from an HTTP request, provided the other tool can send the needed details to the Notis webhook.
What if a required detail is absent?
Ask Notis to report the missing detail for review rather than create a contact with guessed information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Calendarhero. A trigger fires from one place; an action lands in another.
Stripe triggers
Calendarhero actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Calendar Connection
Tool to add a calendar integration to a user's account. use after gathering provider credentials.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact. use after confirming contact details before making the api call.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create Meeting Request V2
Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Fetch Contact
Fetch contact
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Fetch Meeting Details
Tool to fetch details for meetings within a specified timeframe. use this after user provides start and end datetimes in iso8601.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Fetch User Profile
Tool to fetch the profile details of the authenticated user. use after obtaining a valid access token.
Product Created Trigger
Triggered when a product is created in Stripe
List Meetings
Tool to retrieve the user's meetings within a specified timeframe. use after confirming date range to fetch raw calendar data.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
List Meeting Templates
Tool to list all meeting templates available for quick scheduling. use after authenticating and when you need to retrieve available templates before scheduling.
Connect any two apps with Notis in the middle.
Stripe and Calendarhero, 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 Calendarhero.