What the blueprint library covers
Each Forge product is a complete, documented automation system. Three components ship with every blueprint, and the library spans the processes that cost growing teams the most time.
Zapier and Make.com automations
The core of every product is the workflow itself, exported as a JSON file you import directly into your own Zapier or Make.com account. Multi-step logic, conditional branches, filters and error handling are already built and tested.
Steps are named and ordered so the build reads clearly when you open it, which matters the first time you need to change something.
Blueprints are published for both platforms where the process suits both, so you work in whichever tool your team already knows.
Step-by-step setup guides
Every blueprint ships with a setup PDF. It covers the apps you need connected, the order to connect them in, every field that needs mapping, and the test records to run before going live. Known failure points are called out with the fix beside them.
The guides are written for the person doing the work, not for someone who already understands the platform. No prior automation experience is assumed.
Custom API webhook payload templates
Where a blueprint touches a system without a native integration, we supply the webhook payload template written out in full. Correct structure, correct field names, correct formatting, with notes on authentication and the response to expect.
This is the part that usually stops a build. Supplying it finished is what lets a blueprint reach the tools that matter to you rather than only the popular ones.

