The Library and Workbook
The nineteen blueprints, and the spreadsheet they read and write, already built.
€49.97 EURThe Library, Workbook and Slack
Everything in the workbook tier, plus a Slack version of every scenario that notifies your team.
Twelve of the nineteen send a notification to somebody inside your business. Each of those twelve has a second file here with the email module replaced by Slack, the message rewritten in Slack markup, and the recipient setting changed from an address to a channel. Nothing else about them differs, because they are generated from the email versions rather than rewritten by hand.
Only twelve convert. Four of the nineteen email a customer, and you cannot post a customer into a Slack channel; the other three send nothing at all. The guide is explicit about which is which and about never running both versions of a scenario that writes to the spreadsheet.
What you receive
| Item | Detail |
|---|---|
| Blueprint files | 31 x .json |
| Setup guide | PDF, 30 pages |
| Workbook guide | PDF, 4 pages |
| Slack edition guide | PDF, 3 pages |
| Reconciliation workbook | 1 x .xlsx, 10 tabs with working formulas |
| Diagrams | 5 annotated images |
| Sheet templates | 7 x .csv |
| Licence | Plain text file, single business |
What each scenario does
- Twelve Slack variants. Team notification, review alerts, lead capture and handover, four digests, the reconciliation report, refund alerts, the unassigned alert and the health check. Each posts to a channel named in its settings, so moving it is one field.
- Generated, not rewritten. The variants are produced from the email versions at build time, so a correction to a blueprint reaches its Slack twin automatically. The build refuses to ship a variant that still contains an email module or whose channel is mapped from the wrong module.
- Guidance on which to use where. A three page guide covering the Slack connection, the invite step everybody misses, Slack markup for when you reword a message, and the five scenarios that are safe to run in both versions against the seven that are not.
What you need before you buy
- A Make.com account. Most scenarios here run on the free plan. Where one needs a paid tier, the setup guide says so on the first page of that section.
- A Slack workspace, and permission to install an app in it. In most workspaces that means an administrator.
- Everything The Library and Workbook needs.
Screenshots
Scenario screenshot to be supplied
Refund policy
You can ask for a refund within 14 days of purchase. Email support@kettleford.com from the address you bought with, and say which product it is. You do not have to give a reason.
Refunds are returned to the card you paid with. They usually appear within five to ten business days, though that is your bank's timing rather than ours. The seller issues the refund directly; there is no third party you need to chase and no committee to persuade.
Because these are files you download, we cannot take them back. Asking for a refund ends your licence to use them, and you agree to delete the copies you hold, including any you have imported into a Make.com account.
If a blueprint will not import, or a step in the documentation does not work as written, tell us before you ask for a refund. We would rather fix it, and a fix helps the next buyer too. If we cannot fix it, you get the refund whether or not the 14 days have passed.
We do not refund a purchase because a scenario needed a paid Make.com plan or an app you do not have. Every product page lists what you need before you buy, under "What you need before you buy". Please read it.
The full refund policy page adds the sections on returns, cancellation and EU and UK consumer rights.
Licence
- Use it inside one business, across as many Make.com accounts as that business owns.
- Change anything you like. It is your copy once you have it.
- You may not resell it, give it away, or publish the blueprint files anywhere public.
- To deploy it in a client's own Make.com account, you need the Agency Licence.
The full licence terms set out the standard licence, the client deployment licences and the Agency Licence together.
Questions
Why not all nineteen?
Four email a customer, so there is nothing to convert; three send no message at all. Converting the four would mean posting your customers' business into a staff channel instead of emailing them, which is not the same feature.
Can I run the email and Slack versions together?
For five of them, yes, and you get the same alert in two places. For the other seven, no: they write to the spreadsheet, and two copies means every row written twice and the deduplication quietly breaking. The guide lists which are which, and the honest advice is to run one.
My messages post but look wrong.
Almost always double asterisks. Slack bold is one asterisk, not two. The guide has the formatting table and a list of the Slack errors Make actually returns, starting with not_in_channel, which is the one everybody hits first.
Something not answered here? Email support@kettleford.com before you buy. We reply within one US business day, Monday to Friday.
Also worth looking at
The Library
Nineteen scenarios covering orders, reviews and leads, plus two that watch the other seventeen.
€39.97 EURThe Vault
Every blueprint, the workbook and the Slack versions, plus a register of every setting in one sheet, and everything released in the twelve months after you buy.
€119.97 EUR