Resources · Make integration

Sorry Make integrationAutomate Sorry with Make.

Can Make update your Sorry pages, notices and subscribers for you? Yes. The Sorry Make integration gives you 34 modules, including 5 scheduled triggers. This guide connects your API token, builds a first scenario with no code and explains every module.

Try the Sorry integration on MakeSee the 34 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sorry Make integration do for you?

The Sorry Make integration links your Sorry account to Make so that pages, components, notices, updates, subscribers and brands can be read or changed by a scenario, the automation you build in Make from a chain of modules. Each module is one brick: a trigger that starts things, an action that changes something, or a search that finds items.

Post a notice straight from your alerting tool. When another app raises an alert, Create a Notice writes it into Sorry, and Create an Update adds follow-up text as the situation evolves. A support lead stops retyping the same message in two places.

Keep subscribers in line with your CRM. Watch Subscribers brings Sorry subscribers into a scenario so a sales or success team sees them in its own tool. The reverse works too: Create a Subscriber or Update a Subscriber runs when a customer record changes elsewhere.

Hand page details to whoever asks. List Pages and Get a Page pull what Sorry holds, so an ops team can drop it into a sheet or a chat message on request.

What to keep in mind: the Sorry documentation in Make gives no description for its modules and warns that its text is AI-generated, so test each module with Run once before relying on it. Anything the list misses goes through Make an API Call. To judge the platform first, read the Make review. If n8n is also on your list, the n8n vs Make comparison puts both side by side, and Make pricing details the plans.

Connect

How do you connect Sorry to Make?

  1. 01

    Add a Sorry module and click Create a connection

    Drop any Sorry module into your scenario, then click Create a connection. A connection is your Sorry account linked to Make once and reused by every Sorry module. The Connection name field is optional, but a clear label helps later.

  2. 02

    Copy your API token from Sorry

    In Sorry, go to My Account, click API Tokens and copy the token displayed on screen. The token is generated for your own user, so you need an active Sorry account before this step.

  3. 03

    Paste the token and save

    Back in Make, paste the token into the connection window, or follow the on-screen instructions, and confirm. From then on, Make can list the Sorry items it reads directly in the module fields, so you pick them instead of typing IDs.

First scenario

Your first Sorry scenario in Make

GoalWhen your alerting tool flags a problem, Make creates a notice in Sorry for you.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Choose the app that raises your alerts, a monitoring tool or a form, and connect it.

  2. 02

    Add Create a Notice

    Click the + on the right of that first module, search for Sorry and pick Create a Notice. Click Create a connection and paste the API token copied from Sorry.

  3. 03

    Map the alert into the notice

    Fill the notice fields by mapping data from the first module. Each bundle, meaning each alert passed along the chain, becomes a separate notice in Sorry.

  4. 04

    Test with Run once

    Click Run once and fire a test alert. Open the bubble above each module to read the bundles it received, then check that the notice shows up in Sorry.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on a bundle counts as an operation on your Make plan.

Triggers

What can start a Sorry scenario?

5 modules start a scenario when something happens in Sorry. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Sorry as soon as it happens.

Sorry1Watch Components

Watch Components

triggerIn the docs only

Watch Components pulls the components of your Sorry account into a scenario, so whatever Make finds there can kick off work in other tools, like a post in your team chat or a row in a tracking sheet.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the module carries a clock badge.
When to use it
a dashboard or spreadsheet outside Sorry has to mirror your component list without anybody copying it.
Watch out
on the Free plan, Make waits at least 15 minutes between two checks, so the reaction comes after a delay.
Sorry2Watch Notices

Watch Notices

triggerIn the docs only

With Watch Notices, the notices published in Sorry become the starting point of a scenario. Each notice Make picks up travels as a bundle to the next module, ready to be forwarded to email, chat or a ticketing tool.

How it fires
scheduled. Make checks the app on the scenario's schedule and never gets a push from Sorry.
When to use it
your support desk wants every Sorry notice echoed in the channel it already reads.
Watch out
pair it with a notice-creating module in the same scenario and you risk feeding the trigger its own output.
Sorry3Watch Pages

Watch Pages

triggerIn the docs only

Watch Pages keeps an eye on the pages of your Sorry account and hands them to the following module. It is the entry point when page information needs to land in a documentation space, a CRM or an internal inventory.

How it fires
scheduled. Make checks the app on the scenario's schedule, set on the clock of the first module.
When to use it
an agency running Sorry pages for several clients wants a central list kept current.
Watch out
Sorry's module docs carry no description, so run it once and read the bundle before mapping anything downstream.
Sorry4Watch Subscribers

Watch Subscribers

triggerIn the docs only

Watch Subscribers turns the people subscribed in Sorry into bundles your scenario can route anywhere: a CRM contact, a newsletter list, a customer success sheet. Nobody has to export the list by hand again.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the moment somebody subscribes.
When to use it
account managers want to know which customers follow your Sorry page without logging into it.
Watch out
each subscriber processed downstream costs operations, one per module per bundle, so filter early if the list is long.
Sorry5Watch Updates

Watch Updates

triggerIn the docs only

Watch Updates brings the updates written in Sorry into Make, so the follow-up text your team posts can reach people who never open Sorry, through chat, SMS or a shared log in another app.

How it fires
scheduled. Make checks the app on the scenario's schedule; lower the interval on a paid plan, where it can go down to 1 minute.
When to use it
management wants each new update relayed to an internal channel automatically.
Watch out
on the Free plan the gap between checks stays at 15 minutes or more.
Modules

Every Sorry module in Make, explained

Sorry gives you 29 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Sorry1

Create a Component

ActionIn the docs only

This action adds a new component to Sorry from data coming out of another module, so your list of monitored parts grows without a trip to the Sorry interface.

When to use it
a new service goes live in your inventory tool and should appear in Sorry right away.
Watch out
run it once on test data first, as every bundle produces a separate component.
Sorry2

Create a Notice

ActionIn the docs only

Create a Notice publishes a fresh notice in Sorry using whatever your scenario mapped into it, typically the text of an alert raised by another tool.

When to use it
your monitoring or form app detects a problem and customers should hear about it without anyone typing.
Watch out
avoid placing it after Watch Notices in the same scenario, or the new notice may restart the loop.
Sorry3

Create a Page

ActionIn the docs only

Need a brand new Sorry page for a client or a product line? This module creates it from the scenario, using names or settings mapped from an earlier step.

When to use it
an agency signs a client in its CRM and wants the matching Sorry page set up from that record.
Watch out
a duplicated bundle means a duplicated page, so test with Run once before switching the scenario on.
Sorry4

Create a Subscriber

ActionIn the docs only

Create a Subscriber signs a person up to Sorry from your scenario, which saves you from adding customers one by one when they already sit in another tool.

When to use it
a new account closes in your CRM and that customer should follow your Sorry page from day one.
Watch out
check with List Subscribers first when the same person could already be registered.
Sorry5

Create an Update

ActionIn the docs only

Where Create a Notice opens the story, Create an Update adds the next chapter: follow-up text posted to Sorry from the scenario as things progress.

When to use it
your engineers log progress in a ticket tool and the public side should reflect each new comment.
Watch out
the Sorry docs in Make do not say which item an update hangs on, so run it once and read the bundle before mapping anything.
Sorry6

Delete a Brand

ActionIn the docs only

Delete a Brand removes a brand from your Sorry account as part of a scenario, useful when brands follow the life cycle of clients or products managed elsewhere.

When to use it
a client contract ends in your CRM and its brand has to disappear from Sorry as well.
Watch out
nothing comes back after a delete. Add a filter first, then try it on a dummy brand with Run once.
Sorry7

Delete a Component

ActionIn the docs only

Retired a service? Delete a Component takes the matching component out of Sorry so your page no longer shows something that does not exist.

When to use it
your inventory sheet marks a system as decommissioned and Sorry should follow without manual cleanup.
Watch out
the deletion is final, so map the component carefully and try it on a test item with Run once.
Sorry8

Delete a Notice

ActionIn the docs only

This module wipes a notice from Sorry when your scenario decides it should go, for instance a test notice or a message posted by mistake from an automation.

When to use it
a false alarm is confirmed in your alerting tool and the notice it generated must vanish.
Watch out
nothing brings the notice back afterwards, so keep a filter that checks the reason before deleting.
Sorry9

Delete a Page

ActionIn the docs only

Delete a Page removes an entire Sorry page, the heaviest cleanup action of the app, typically at the end of a client relationship or a product.

When to use it
an offboarding scenario closes everything linked to a departing client, the Sorry page included.
Watch out
there is no undo from Make; put a strict filter just before this module and test it on a dummy page.
Sorry10

Delete a Subscriber

ActionIn the docs only

When somebody should stop hearing from you, Delete a Subscriber takes that person off your Sorry list from inside a scenario.

When to use it
a contact unsubscribes in your email tool or leaves a customer account, and Sorry must respect it too.
Watch out
deleted subscribers are gone for good, so find the right one with List Subscribers before mapping the reference.
Sorry11

Delete an Update

ActionIn the docs only

Delete an Update erases a single update from Sorry and leaves everything else as it is, handy when only one message went wrong.

When to use it
an automation posted an update with a wrong status and you want the correction to follow the same path.
Watch out
the update cannot be recovered afterwards, so double check which reference you map.
Sorry12

Get a Brand

ActionIn the docs only

Get a Brand fetches the details of a single Sorry brand so later modules can reuse them, for example to label a report or a message with the right brand.

When to use it
you already hold the brand reference from an earlier step and need its full record.
Watch out
it reads one brand only; the module needs a reference to look up, it does not browse.
Sorry13

Get a Component

ActionIn the docs only

Pick Get a Component when your scenario knows which component it cares about and needs everything Sorry stores about that one item before acting.

When to use it
an alert names a component and you want its current details before writing a notice.
Watch out
unlike List Components, it returns a single bundle, so feed it a precise reference mapped from a previous module.
Sorry14

Get a Notice

ActionIn the docs only

Get a Notice reads one notice from Sorry in full, giving the next modules the text and details to forward, archive or compare.

When to use it
a teammate shares a notice reference in a chat command and wants the full content sent back.
Watch out
the module does not search; without a notice reference mapped in, it has nothing to read.
Sorry15

Get a Page

ActionIn the docs only

This read-only module brings back the record of a single Sorry page, which is useful when later steps need its details for a report or a client message.

When to use it
an account review pulls the Sorry page attached to each client stored in your CRM.
Watch out
run it once and inspect the bundle, since the Sorry docs in Make do not describe what it returns.
Sorry16

Get a Subscriber

ActionIn the docs only

Get a Subscriber looks up one person already registered in Sorry, so your scenario can check their record before updating or deleting it.

When to use it
a customer asks support about their alerts and the agent triggers a scenario to see their Sorry subscription.
Watch out
it expects a known subscriber reference; to find somebody by browsing, start with List Subscribers.
Sorry17

Get an Update

ActionIn the docs only

Get an Update retrieves one specific update from Sorry, giving you its content to copy into a postmortem document, a ticket or a message.

When to use it
Watch Updates hands over a reference and you want the complete update before forwarding it.
Watch out
each call counts as an operation, so skip it when the trigger bundle already carries what you need.
Sorry18

List Components

SearchIn the docs only

List Components is a search: it returns every component Sorry holds as separate bundles, which lets the next modules handle them one after another.

When to use it
you need an on-demand snapshot of all components for an audit sheet or a health report.
Watch out
a search can return zero, one or many bundles, and each one downstream costs operations.
Sorry19

List Notices

SearchIn the docs only

Use List Notices to collect the notices stored in Sorry in one pass, for example to build a history in a spreadsheet or to review what was published.

When to use it
a quality manager prepares a review of past incidents and wants every notice gathered in one place.
Watch out
an empty result means the following modules simply do not run, which is normal for a search.
Sorry20

List Pages

SearchIn the docs only

List Pages walks through all the Sorry pages you can access and outputs each as its own bundle, the natural first step for anything that touches every page.

When to use it
an agency wants a per-client table of Sorry pages refreshed from a button in its tools.
Watch out
combine it with a filter before any update or delete module, or the change hits every page returned.
Sorry21

List Subscribers

SearchIn the docs only

List Subscribers pulls your Sorry audience into the scenario, one bundle per person, ready to compare with a CRM or a mailing list.

When to use it
marketing wants to reconcile who follows your Sorry page with who is a paying customer.
Watch out
long lists add up fast in operations; place a filter right after the module to keep only what matters.
Sorry22

List Updates

SearchIn the docs only

List Updates gathers the updates stored in Sorry so a scenario can archive them, count them or send a digest to people outside the tool.

When to use it
a team lead wants every follow-up posted in Sorry compiled into a shared document.
Watch out
the search may return many bundles; add an aggregator if you want one combined message instead of many.
Sorry23

Make an API Call

ActionIn the docs only

Make an API Call is the escape hatch: it lets the scenario call any endpoint of the Sorry API with the connection you already set up, covering what the listed modules leave out.

When to use it
you need a Sorry operation that none of the 34 modules offers.
Watch out
you write the request yourself, so keep the Sorry API docs open and test each call with Run once.
Sorry24

Update a Brand

ActionIn the docs only

Update a Brand edits an existing Sorry brand from your scenario, so a change made in your client records does not have to be repeated in Sorry.

When to use it
a client renames itself in your CRM and its Sorry brand should carry the new details.
Watch out
map only the values you want to change and test on a single brand before activating.
Sorry25

Update a Component

ActionIn the docs only

Update a Component changes a Sorry component in place, the module to reach for when an outside signal should alter what your page says about a system.

When to use it
your monitoring tool reports that a service is back and the component should reflect it.
Watch out
a wrong reference edits the wrong component, so fetch it with Get a Component or List Components first.
Sorry26

Update a Notice

ActionIn the docs only

Rather than posting a new message, Update a Notice rewrites an existing Sorry notice, for example to fix its wording.

When to use it
the incident is closed in your ticket tool and the original notice should say so.
Watch out
if you want a trace of each step, Create an Update fits better than overwriting the notice.
Sorry27

Update a Page

ActionIn the docs only

Update a Page modifies the settings or content of a Sorry page from a scenario, keeping it in step with decisions made in other tools.

When to use it
a product changes name in your catalog and its Sorry page must follow.
Watch out
after List Pages, the module runs once per bundle, so filter to the single page you mean to change.
Sorry28

Update a Subscriber

ActionIn the docs only

Update a Subscriber refreshes the record of a person already on your Sorry list, so contact changes in your CRM reach Sorry without double entry.

When to use it
a customer switches email in your billing tool and should keep receiving your notices.
Watch out
the subscriber must exist; for new people, Create a Subscriber is the right module.
Sorry29

Update an Update

ActionIn the docs only

Update an Update corrects an update already posted in Sorry, which saves deleting it and posting a new one when only a detail was off.

When to use it
a typo or a wrong time slipped into an automated update and the fix comes from your ticket tool.
Watch out
the old text is replaced, not kept, so use Create an Update when the history should stay visible.
Need help

Need help automating Sorry with Make?

A person reads every message.

FAQ

Sorry and Make: common questions

01Is the Sorry Make integration free?
Yes, Sorry is a standard app, so it works from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations, one per module per bundle. You still need your own Sorry account.
02What do you need to connect Sorry to Make?
You need an active Sorry user account and a personal API token. In your Sorry account settings, open the API Tokens section and copy the token shown on screen. In Make, add a Sorry module, click Create a connection, give it a name if you like and paste the token. The connection is then reused by every Sorry module in your scenarios. Because the token is tied to a user, create it from an account your team will keep.
03Do Sorry triggers in Make fire instantly?
No. All 5 Sorry triggers are scheduled: Watch Components, Watch Notices, Watch Pages, Watch Subscribers and Watch Updates. Make checks Sorry on the schedule set on the first module, every 15 minutes by default. On the Free plan the gap cannot drop below 15 minutes; paid plans allow 1 minute. There is no instant trigger for Sorry, so a scenario reacts at the next check rather than the second something changes in your account.
04What if a Sorry module is missing in Make?
Use Make an API Call. This module calls any endpoint of the Sorry API from your scenario, with the same connection as the other Sorry modules, so you are not limited to the listed actions. You write the request yourself, so check the Sorry API docs and test with Run once. Also note that the Sorry documentation in Make carries no module descriptions and flags its content as AI-generated, so verify the output of each module before building on it.
05Should you use Make or n8n for Sorry?
It depends on the tool your team already runs. On Make, Sorry comes with 34 modules: 5 scheduled triggers, 24 actions and 5 searches, plus Make an API Call for anything else, all available from the Free plan. The same app often has an n8n node too, so check what exists there before choosing. Pick the platform where your other scenarios already live, since one place to maintain connections and monitor runs is simpler for the team.
Same platform

Other docs you might need on this stack.

Browse all integrations