Settings, Connections starts with the apps the business connects, the same list as Admin, Apps: each is connected there the one way, at the service's own sign-in or with the keys you make there, checked, sealed and never shown again (see Connect your apps). Below them come the settings of the apps connected, your booking page on other sites, and the API. From then on, what happens here is passed along as it happens. Settings, Approvals is where the rules for programs and AI live, and the changes that wait for a person. With more than one business, Admin, Tools shows what each has linked, and opens each one's Connections (see Admin).
For your clients
- Booking on your own website: paste one line into your site and a Book button appears in your colors. It opens your booking page over the site, so nobody leaves it. Works on Shopify, Squarespace, Wix, WordPress and plain HTML.
- Book from social: your booking link with a tag on the end for each place you post it (Instagram, Facebook, TikTok), so you can see which one brings the bookings.
- Google reviews: find your business on Google and link it, from its app under Apps. Your rating shows on your website and receipts, follow-ups ask for a review with the right link, and the latest reviews show here.
For your other tools
- Klaviyo and Mailchimp: connect them under Apps with the key you make there; your clients go to the audience you choose, with what they agreed to.
- Shopify: for a business that sells its own products in a Shopify store. Orders the store has shipped come in by themselves, about once an hour, and take the stock out of the place you choose, matched by SKU to your part numbers or barcodes. It only reads orders; it never changes anything in your store.
- Calendar feeds: a private link each person adds to Google Calendar, Apple Calendar or Outlook once. Their visits then show there and keep themselves up to date. It goes one way. Anyone with a link can read that calendar, so give each person only their own.
- ADP payroll: the app works out hours, commission and tips; ADP pays people and files the taxes. Pick which ADP you run payroll on (RUN Powered by ADP or Workforce Now), and connect ADP from its app with your company code and the client id and secret ADP gave the business: from your subscription to this app on ADP Marketplace once you subscribe and consent there, or from your own API Central project on Workforce Now (then you may bring its certificate too). They are tried against ADP, kept sealed and never shown again. Your earnings codes are set on the ADP card here. Check the connection says whether ADP answers. Under Who Is Who at ADP, each team member is matched to ADP's worker by file number, the unmatched offered the closest name. Then each pay period goes from Time & Pay, Pay with Send this pay period to ADP (see Time and pay).
- Enrichment: Apollo, LinkedIn and Clay: Enrich on a lead, a prospect, an account or a vendor fills in its blanks (website, phone, address, industry, size, social links, the people who run it) from the provider you connect under Apps with your own key, which is checked, kept sealed and never shown again; you accept what it proposes field by field, and the record says what came from where. Apollo and LinkedIn (through Proxycurl) answer at once. Clay is a round trip: paste your Clay table's Webhook source address here, and end the table's workflow with an HTTP API step that posts the row as JSON to the address shown on the card, with the row's
callback_tokenin it; the app matches the row's columns by name (website, phone, email, address, city, state, zip, industry, employees, linkedin_url, description, and apeoplelist with name, title, email, phone and linkedin). Set the cap on lookups a month here; this month's count shows beside it. Read the sales CRM for accepting a proposal.
Your own AI assistant
The way to connect Claude, ChatGPT, or anything else that speaks MCP, is now to add BookNovi's address to the assistant and sign in as yourself: each person on the team connects their own, it reaches only what their login reaches, and it can make changes, each said back to them first. Read Talk to BookNovi from Claude or ChatGPT; the address is under Assistants and voice in your own menu, and under Settings, Assistants and voice.
The private links made here before that still work, and only read:
- An owner opens AI assistants under Apps and chooses Make a link.
- Say Which assistant is it for and What it may read: the calendar, clients, sales and reports, inventory. Services, prices and the team are always included.
- Copy the link (it is shown this once) and paste it into the assistant as a connector.
A link can only read, never change anything, and never sees notes, formulas or forms. It can also read this Help. Switch a link off at any time. A link reads no more than the person who made it may see: each part it is given is read through that person's own switches, so a part their login does not have is refused by name, and a switch turned off for them later narrows the link with it.
API keys for programs and AI agents
For your own programs and the services you connect, such as a marketplace, a warehouse or an accounting tool.
- An owner chooses Make a key under API keys.
- Say What it is for, Who uses it (A program, or An AI agent), what it may read and what it may do.
- Copy the key (shown this once) and keep it on a server, never in a website or a phone app.
A key changes only what you allow, through the same rules as the app: stock moves in the ledger, customers get their emails, and every change shows in the activity log with the key that made it. As with a link, a key reaches no more than the person who made it may see: a part their switches do not open is refused when the key is made, and a switch turned off for them later narrows the key. The API reference at /developers describes every call; an AI agent learns the business a layer at a time from the describe call.
Webhooks and Zapier
Under Webhooks and Zapier, Add a webhook: give a link, and each booking, order, shipment, product change, finished visit, sale and new client is posted to it as it happens. In Zapier or Make, start with "Webhooks: Catch hook" and paste the link it gives you. Send a sample to test it. Each post is signed with a secret shown once.
What programs and AI may do
Open Settings, Approvals. For each change a key can make, an owner chooses Do it, Ask first or Never, separately for programs and for AI. By default, programs do it at once, and AI asks first. Reading is never held: a key reads only what it was given. The rules for AI apply as well to the assistants each person connects as themselves (see Talk to BookNovi from Claude or ChatGPT): with Ask first, what they say yes to through Claude or ChatGPT waits here under their name, such as "Dana Reyes through Claude". Whatever the rules say, an assistant never changes permissions, roles or logins, security settings or connections that hold sign-ins, or bank, payout or card details; never exports everything; never closes the business; never deletes a record for good; and never takes the brake off spending, by starting a paused wallet again or changing when the pay-as-you-go tools need a sign-off (see Pay-as-you-go tools and the wallet).
Changes held for a person wait under Approvals, with a count beside Settings. Approving does it then, as the key that asked, with the same checks as the app; declining tells them no. A change not decided in 7 days lapses. The assistant in the app always shows its changes as a card for the person who asked.
Best practices
- Give each program its own key, with only what it needs. Turn a key off the day you stop using the service.
- Mark keys used by an AI agent as An AI agent, so your rules for AI apply to them.
- Leave changes that cost money or reach customers (buying a label, booking freight, posting a count, setting a sales goal) on Ask first for AI.
- Give each person their own calendar feed, never a shared one.
- Use a webhook with Zapier or Make for anything not listed here before asking for a custom build.