Forms, Booking & Automation Tools
Connect Typeform, Tally, Calendly, Cal.com, SavvyCal, Google Appointments, and Instagram via Manychat to Nashra. Covers the landing page Booking section (bookers join your audience, "Booked a call" on their Journey), embeds, HTML form action URLs, and when you need a connector like Zapier or Make.
How outside tools reach Nashra
Every tool on this page sends people to Nashra the same way: an HTML form endpoint. Create one under Settings → Forms → New HTML form, then copy its endpoint URL. For a tool that calls the URL from its own servers, set Response type to JSON. Redirect is for a visitor's browser, and it needs a Thank-you URL.
The endpoint reads plain, top-level fields:
| Field | Name |
|---|---|
| Email (required) | email |
| Name | first_name, last_name |
| WhatsApp number (optional) | phone, in full international format, or a local number plus phone_country (a two-letter code like AE) |
| Custom fields | Each field's key |
It doesn't unpack a tool's own payload format. A tool that lets you write the request body yourself, like Manychat, can post straight to it. A tool whose webhook sends a fixed payload, with the email buried inside it, needs a connector like Zapier or Make in between to map that answer to email. See HTML Forms & Form Actions for everything the endpoint accepts.
Form tools
Typeform and Tally
Typeform and Tally aren't page builders. They're standalone forms that send each response to a webhook. Their webhooks use their own payload format: the email sits inside a list of answers, not in an email field. So pointing a webhook straight at your Nashra endpoint gets the submission rejected.
Create the Nashra side
In Settings → Forms, click New HTML form, set Response type to JSON, add any Auto-tag submissions tags, and copy the endpoint URL.
Add a connector
In Zapier, Make, or a similar tool, start from "new Typeform response" or "new Tally submission". Add a step that sends a POST request to your endpoint URL, mapping the email answer to email (and the name to first_name, if you ask for it).
Test with a real response
Submit the live form once and check that the person appears on your Audience page.
Both tools also offer a redirect on completion setting. That's separate from the webhook. Use it to send the respondent to a Nashra landing page or your Hub as a next step, not as the way their email reaches Nashra.
If all you need is an email signup, you may not need Typeform or Tally at all. A landing page's Signup section or a Resource collects the email, name, and an optional WhatsApp number natively, with no connector.
Booking and scheduling
Book on your own page
The simplest setup doesn't send anything to Nashra. You put the scheduler on a page Nashra already hosts, and the page does the capturing.
Open a landing page
From the Library, create or open a landing page.
Add a Booking section
Pick a layout. Card and Beside calendar sell the call first, with short details like "30 min" or "Free". Calendar puts the scheduler straight on the page.
Paste your booking link
Paste a Calendly, Cal.com, or SavvyCal event link.
Keep Ask for email first on
On the Card and Beside calendar layouts, Ask for email first is on by default. Add a Tag on signup, like discovery-call, if you want to find these people later. Then publish.
With Ask for email first on, a visitor gives their name and email before picking a time:
- They join your audience through the page, the same way a Signup section works. They're tagged with the section's Tag on signup, and they start any automation triggered by "Person subscribes via
page name(Landing page)". If double opt-in is on, they're Unconfirmed until they click the confirmation email. - The scheduler opens with their details filled in, so they don't type them twice.
- The booking lands on their Journey. When the scheduler is Calendly, a completed booking shows as Booked a call on the person's Journey and marks them Showed interest. Cal.com and SavvyCal don't tell the page when a booking completes. Those bookers still join your audience, but the booking itself isn't recorded.
The Calendar layout has nowhere to ask first. It shows the scheduler only, so it doesn't add new people to your list.
Links to Calendly, Cal.com, and SavvyCal count as offer links everywhere. Anyone who clicks one in your emails is marked Showed interest too, whichever page they book on. See What counts as an offer link.
Google Appointments
Google appointment schedules don't have a Booking layout, but you can still put one on your page. Add an Embed section and paste the embed code Google gives you for the schedule. The scheduler shows up, but it doesn't collect an email for Nashra. Add a Signup section next to it if you want bookers on your list.
Sending bookings from the tool itself
To capture bookings made anywhere, not just on your Nashra page, the booking tool has to send them out. Calendly and Cal.com can send new bookings to a webhook, but in their own payload format, so put a connector like Zapier or Make in between. Trigger on a new booking, then POST the invitee's email to your endpoint as email.
Google doesn't offer a no-code way to send out appointment bookings. For most workspaces, embedding the booking page is the whole integration.
Chat and social automation
Instagram via Manychat
Manychat automates Instagram DMs: comment-to-DM, keyword replies, multi-step chat flows. Common patterns are a "comment GUIDE to get the link" flow, or a keyword reply that asks for an email before sending a lead magnet. When a flow collects someone's email, Manychat's External Request action can hand it to Nashra. You write the request body yourself, so no connector is needed.
Collect the email in your flow
Add a step that asks for an email and saves the reply as a Manychat user field. Collect a phone number too if you want it on the subscriber's profile.
Create the Nashra side
In Settings → Forms, create a New HTML form with Response type set to JSON, and copy its endpoint URL.
Add an External Request action
In the flow builder, add External Request, Manychat's built-in HTTP call. Set the method to POST and the URL to your endpoint.
Map the fields
In the JSON body, map the saved email to email. Optionally map the first name to first_name and the phone number to phone (full international format).
Test it
Run the flow yourself before turning it on for everyone, and check that you show up on your Audience page.
Give this HTML form an Auto-tag submissions tag, like instagram-manychat, so you can see exactly how many subscribers came from the flow. See Auto-tagging.
Quick reference
| Tool | Primary pattern | Also supports |
|---|---|---|
| Typeform | Connector (Zapier, Make) → endpoint | Redirect on completion |
| Tally | Connector (Zapier, Make) → endpoint | Redirect on completion |
| Calendly | Booking section, Ask for email first (booking recorded on the Journey) | Connector → endpoint |
| Cal.com | Booking section, Ask for email first | Connector → endpoint |
| SavvyCal | Booking section, Ask for email first | — |
| Google Appointments | Embed section | — (no no-code push) |
| Instagram (Manychat) | External Request → endpoint | — |
Every path that posts to your endpoint shares its rate limit: 10 signups a minute from any one IP address. Connectors and Manychat send from their own servers, so a busy launch can reach that limit. See Rate Limits.
What's next
Landing Pages
Build the page your Booking or Signup section lives on.
HTML Forms & Form Actions
Fields, tags, and response types for any endpoint.
Audience
See bookers on their Journey and find the people who showed interest.
Website Builders
The same endpoint pattern for Framer, Webflow, Elementor, and Carrd.