View all app connections
View all AI automations
View all chatbots
View all lead automations
View all booking automations
View all payment automations
View all workflows
View all Shopify
View all WooCommerce
View all HubSpot
View all Salesforce
View all Stripe
View all Google Sheets
View all Slack
View all dental practice
View all law firm
View all medical practice
View all real estate
View all restaurant and food
View all home services
View all construction
See all: get more leads
See all: get paid faster
See all: save admin time
See all: support customers
See all: book more appointments
See all: sell more online
See all: hire and onboard
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations

BoldBellowsA card, not a text line

Squarespace to Microsoft Teams, posted as a card worth acting on, not a message worth ignoring

We build a sync that lands each Squarespace order in your Teams channel as a proper Adaptive Card, fields laid out cleanly, with an Approve or Flag button for the builds that call for one. Nothing about your Squarespace store gets touched in the process.

View Pricing

Billed once, starting at $425
Microsoft 365 licensing stays separate

  • Works with any Teams channel you already use
  • Store data comes across one direction only
  • Builds tend to wrap up in about ten days
Squarespace to Microsoft Teams automation by BoldBellows: an order posted as an Adaptive Card with fields laid out and an approve button, not a plain text notification
Card posted: #7701 Awaiting approval
Plate I. A card with something to click, not just something to read.
  • Proper cards Fields laid out, not one long line
  • Store left alone Data flows out, never back in
  • Routed sensibly Not every order dumped in one channel
  • Your tenant Nothing routed through a third party first
  • From $425 Billed once, that's the last of it

Chapter 01The flat-notification habit

Teams treated like a Slack channel with a different logo

The fastest way to wire Squarespace into Teams is a plain text webhook message, same as you'd post into Slack. It works, technically, but it leaves everything Teams can actually do with a card sitting unused.

We paid for Teams because it's already how the company works, and our order alerts still looked like something copy-pasted from a Slack setup. No card, no fields, nothing to click.

A pattern that shows up often in a first look at a Teams setup

One long line per order

Everything crammed into a sentence means scanning past text to find the one number that actually matters.

Nothing to click, ever

A high-value order that genuinely needs a second look gets the same passive treatment as a routine one.

One channel, every order

A $15 candle and a $600 commission land in the same place, at the same volume, with the same priority.

Before

#GENERAL · PLAIN TEXT ONLY New order #7701, total $64.00, from A. Reyes. New order #7702, total $212.00, from J. Ortiz. New order #7703, total $612.00, from M. Diaz. ? The $612 order needed a second look
Fig. 2a. Every order, identical text, nothing that flags the one worth pausing on.

After

Order #7703 · Review recommended CustomerM. Diaz Total$612.00 Approve Flag Routed here because it crossed your review threshold.
Fig. 2b. Fields laid out clearly, and a button that actually does something.

Before

  • Every order squeezed into a single sentence
  • No visual difference between routine and high-value
  • Nothing on the card that can be actioned
  • One channel absorbing every kind of alert

After

  • Fields laid out the way a card is meant to look
  • High-value orders flagged and routed differently
  • An Approve or Flag button wired through Power Automate
  • Channels that stay specific to what belongs in them

Chapter 02How it works

Three parts, one card landing where it should

Three parts sit between your store and a channel that says something useful. Squarespace is checked, never changed; the sync builds the card and, where it applies, decides which channel it belongs in.

Your Squarespace site New and changed orders Checked, not changed The sync we build Builds the card, picks the channel Adaptive Card posted Your Teams channel Something worth glancing at Your site New and changed orders Checked, not changed The sync we build Builds the card, picks the channel Adaptive Card posted Your Teams channel Something worth glancing at
Fig. 3. Routing happens before the card is posted, so it lands somewhere it's meant to.

Squarespace: read, not written to

This build looks at orders and nothing further; your listings, pricing and store settings are never within reach of it.

Posted once, per order

Each order's card is tracked internally, so a later check doesn't post the same order into the channel a second time.

Approvals: real, through Power Automate

Where it's included, clicking Approve on a card actually fires a Power Automate flow, not a static button that does nothing.

Chapter 03The channel

What a posted card actually looks like

This is what shows up in the channel once your package is live, from a bare-bones order card up to one that carries a working approval button.

Teams · Orders channel Last sync 2 min ago Order #7701 A. Reyes · $64.00 Studio Session Order #7703 · Review recommended M. Diaz · $612.00 Approve Flag Orders EscalationsDigestApprovalsSync health
Fig. 4. Orders channel. A routine card and a flagged one, laid out differently on purpose.

Order cards

Every paid order posted once, fields laid out cleanly, no duplicates.

Every package

Channel routing

Orders sorted by category or value, so a busy channel stays focused.

From Channel Router

Approval actions

Approve or Flag buttons on cards over your threshold, wired through Power Automate.

From Approval Command

Sync health

Every post logged, so a card that failed to send is easy to catch and fix.

Every package

Chapter 04Who this fits

Built for teams already living inside Microsoft 365

If your order alerts read like a Slack message that wandered into Teams by mistake, giving them real cards is what actually uses the platform you're paying for.

Teams running order approvals

Someone with authority gets an actual button to click, not a message they then have to act on somewhere else.

Small operations teams

A channel that actually distinguishes a routine order from one that needs eyes on it right away.

Organizations already using Power Automate

An approval card that plugs straight into flows you or your IT team have already built.

Multi-storefront sellers

One tenant, correctly routed regardless of which Squarespace site an order actually came in through.

Chapter 05The options

A few ways to get Squarespace orders talking to Teams

Getting text into a channel is the trivial half of this. Building a card with real fields and an action that actually fires is where most quick approaches stop trying.

Table comparing four ways to get Squarespace order detail into a Microsoft Teams channel as usable cards: typing them in by hand, a Zapier or Make scenario, an off-the-shelf connector app, versus a build made for this exact channel
Question Manual posting Zapier or Make Generic connector app BoldBellows build
Posts a proper Adaptive Card Not without someone building it by hand each time Possible, but usually skipped for a plain message Sometimes, on a higher tier Yes, fields laid out on every card
Includes a working approval action Not something manual posting offers Outside what a generic automation platform wires up Rarely offered at all Wired in through Power Automate, when your package includes it
Prevents duplicate posts Relies entirely on whoever's typing to remember what they posted Possible, if it was built with real care Usually, within its own scope Tracked internally, checked every pass
What it costs over time Free, aside from the time it eats up Costs that scale with how many orders you get Somewhere between $15 and $45 monthly One-off price from $425
Where it lives Your own Teams tenant Routed through a third party's own infrastructure Constrained to that app's fixed card templates Posted straight in, under your tenant's own name

The part that decides if anyone reads it. A wall of plain text trains a team to skim past the channel entirely. A card with clear fields, and an action on the ones that matter, is what keeps people actually checking it.

InterludeA channel worth reading

Turn order alerts into cards your team actually acts on

Three short questions about order coverage, card detail and refresh speed set both the price and the go-live date below, updating live as you answer them. Most channels are live within a week and a half.

View Pricing

From $425, billed once · You own everything we build

Pricing

Build your Squarespace to Microsoft Teams price

Pick a package, answer three short questions about which orders post, how detailed each card is and how often Teams refreshes, and your price and go-live date move as you choose.


Choose your packageRequired

The three packages differ by how much a card carries and whether approval actions are wired in.

Every order posts as a proper Adaptive Card, not a plain line of text.

  • An Adaptive Card posted to one channel for each new paid order
  • Order number, total and item summary laid out as card fields
  • A scheduled re-check on real cron that catches anything the last pull missed
  • Your own read-only Squarespace API key, never a shared public app
  • Handover notes (PDF) covering the card layout and every field
  • Two rounds of changes once you see real cards land

Different order types routed to the channels that actually need them.

  • Everything in the Card Alerts package
  • Orders routed to different channels by product category or value
  • A value threshold that keeps low-value orders out of a busy channel
  • Refunds and cancellations posted with their own card style
  • Handover notes (PDF) covering the full routing logic
  • Three rounds of changes once it is running

High-value orders carry an actual Approve or Flag action, via Power Automate.

  • Everything in the Channel Router package
  • An Approve or Flag button on cards over a threshold you set, wired through Power Automate
  • A response log tracking who actioned which card and when
  • Near-instant refresh so a new order reaches Teams within minutes
  • Handover notes (PDF) covering the full approval flow
  • Four rounds of changes once it is running

Several Squarespace sites feeding one Teams tenant, an approval flow built around your own review process, or a card layout none of the packages above name. Tell us how your team works in Teams and we will price it for your build.

Which orders should post a card?Required

Cast the net wider and the channel stays fuller, but also more current on refunds and cancellations.

How much should a card actually show?Required

More fields on the card mean less time spent tabbing back to Squarespace to check what was actually ordered.

How often should Teams refresh?Required

Squarespace's API is polled on a schedule rather than pushed by webhook, so this sets how often we check back.

How soon do you need it live?Required

Standard follows the schedule your other choices set. Pay to move up the queue and go live sooner.

Optional extrasOptional

Each one begins switched off. Turn on what your channel needs, watch the total, switch it back off.

Chapter 06The build

Six stages between a webhook and a channel worth watching

Each stage hands off to the next until real cards are landing in your channel. Your side of it comes to roughly twenty minutes total, spread across a short setup call and one review pass near the end.

  1. Kickoff

    Mapping cards to channels

    We settle which order types post where, what counts as high-value, and whether any of it needs an approval step before a single card is built.

  2. Ten minutes on your side

    Issuing a key and a webhook

    You generate a read-only Squarespace API key and add an Incoming Webhook to your Teams channel, both from short guides written for this exact step.

  3. Where the time goes

    Building the card and the routing rules

    The Adaptive Card layout goes together first, then the routing logic that decides which channel each order lands in, then any Power Automate approval action your package includes.

  4. Before your channel sees any of it

    Running real orders into a private test channel

    A separate channel only we can see gets the first batch of cards, built from actual recent orders, so a layout or routing mistake never reaches your team.

  5. Your review window

    Clicking through cards the way your team will

    You open the test channel, click any Approve or Flag buttons your package carries, and tell us what to adjust before it moves anywhere live.

  6. Handover

    Switched to your live channel and left running

    Documentation covering the card fields, routing rules and any approval flow arrives at handover, and the sync then runs on its schedule without anyone tending it.

Before we can start building

  • Someone who can generate a Squarespace API key
  • Rights to set up an Incoming Webhook on the channel you've picked
  • Admin rights in Power Automate, if an approval action is in scope
  • A short window near the end to click through test cards

Chapter 07Trust

A channel your whole team can see deserves a narrow connection

Order totals and buyer detail post somewhere everyone with channel access can read, so what feeds it stays deliberately limited on both ends.

Incoming Webhook URL·····webhook.office.com/····· ScopeThis channel only Read-only

The store side of this stays view-only

The API key posting cards into your channel can see order detail and stop there; changing what's for sale, or any other store setting, never enters the picture.

One webhook, scoped to one channel

The Incoming Webhook this build posts through reaches the single channel it was created for; it has no way to post into any other channel or team.

Power Automate runs under your tenant

Where an approval action is part of the build, the flow behind it lives in your own Power Automate environment, not somewhere we host or control.

Pulled in a click, either side

Delete the webhook or revoke the Squarespace key and the connection ends immediately; nothing further needs to be undone on our end.

Order data passes through, not into storage

Fields used to build a card exist only long enough to post it; we keep no separate database of your orders or buyer detail.

One fee, paid once

Your Microsoft 365 and Teams licensing stays your own arrangement; BoldBellows bills a single amount for the build itself and nothing further.

"An approval button in a shared channel is only as trustworthy as the flow behind it. We test every card and every action against orders that actually happened before we call a build done."

Steven GrratFounder, BoldBellows

Chapter 08In their words

What BoldBellows clients say

Verified reviews from business owners running BoldBellows automations across marketing, fulfillment, reporting and more, on the Squarespace to Microsoft Teams route.

AI CRM Automation

Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.

Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.

David KimVerifiedSeoul, South Korea

AI HR & Recruitment Automation

Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.

It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.

Olivia MartinezVerifiedAustin, USA

AI Video & Voice Automation

We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.

The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.

Lucas SteinerVerifiedMunich, Germany

AI Chatbot & Customer Support

BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.

What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.

Maria GonzálezVerifiedMadrid, Spain

AI E-commerce Listings Automation

BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.

It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.

Pedro LimaVerifiedSão Paulo, Brazil

AI Workflow Automation for Agencies

Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.

Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.

Samuel BoatengVerifiedAccra, Ghana

AI Document & Contract Automation

Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.

What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.

Michael O’ConnorVerifiedDublin, Ireland

AI Lead Qualification & Sales Automation

Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.

It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.

Aisha MohammedVerifiedDubai, UAE

AI Translation & Localisation

When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.

The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.

Kenji NakamuraVerifiedOsaka, Japan

Chapter 09Questions

Before a card starts posting into your channel

A running list of what comes up on calls before a channel build gets approved. Anything about your particular tenant setup is best raised straight away when you request a quote.

Do you need admin access to our whole Teams tenant?

No. Posting cards only needs an Incoming Webhook you add to the target channel yourself. An approval action needs Power Automate access, scoped to that flow.

Can different order types post to different channels?

Yes, with the Channel Router package or above. Category, value or status can each send a card to a channel other than your default one.

What happens when someone clicks Approve on a card?

A Power Automate flow in your own tenant records who clicked, when, and updates the card in place so the channel shows the outcome, not just the original request.

Can a second channel handle urgent or escalated orders?

Yes, the second channel for escalations extra adds a dedicated Incoming Webhook so flagged orders post somewhere separate from routine traffic.

Does the channel start empty, or does older order history show up too?

Add the full historical backfill extra and a recent stretch of past orders gets posted as cards too, so the channel isn't only forward-looking from day one.

Can we get one card a day instead of one per order?

Add the daily summary card extra and a single morning card totals the previous day's orders alongside your per-order cards, or in place of them if you'd rather.

Who catches it if a card stops posting one day?

A stalled poll or a rejected card shows up in the sync health log immediately. Add the aftercare extra and we track it down and retune the routing for three months past handover.

Does this add anything to our monthly bills?

It doesn't. You pay for the build one time. Your Microsoft 365 plan carries on exactly as it does today, billed by Microsoft as always.

Let your channel show cards worth clicking

A plain notification gets read and forgotten. A proper card with real fields and, where you need it, a working approval button gets acted on. Answer three questions below to see your price, or tell us about your channel setup and we'll quote it directly. If you searched for squarespace orders teams notification, squarespace microsoft teams integration and squarespace teams alert automation, this is the service that delivers it.

  • From $425, a single fee
  • Cards, not plain notification lines
  • Squarespace, read from and left alone
  • No monthly fee added on top