Category
Builders
Workflow and integration documentation for Boilerplate Builders.
What Builders is for
Boilerplate Builders lets teams create workflow automation without starting from a blank backend project. A workflow is built from connected blocks. Each block does one job: start the workflow, transform data, call an API, send a message, read a file, run AI, or route execution based on a condition.
Core objects
- Project: workspace for pipelines, runs, files, Vault entries, integrations and team access
- Pipeline: a workflow graph made from blocks and connections
- Version: a saved pipeline snapshot; published versions are runnable
- Block: one workflow step, such as a trigger, API request, condition or integration action
- Edge: a connection that decides how data and execution move through the workflow
- Run: one execution of a published pipeline version
- Vault: secure storage for secrets, credentials, integrations and AI agents
- Budget: compute allowance used by workflow execution and platform-billed AI features
Recommended first workflow
Start with an Endpoint Trigger, connect it to a Transform block, publish the version, call the generated endpoint and inspect the run logs. This teaches the basic loop: trigger, data, execution, logs and iteration.
Explore Subjects
Getting Started With BlocksLearn how Builders workflows are assembled from triggers, actions, logic and design blocks.Straight to the topic that interests you:Trigger blocksProcess and data blocksEmail, messaging, queue, issue and SSH action blocksGetting Started With IntegrationsConnect Builders workflows to email, storage, messaging, queues, issues and remote systems.Straight to the topic that interests you:Mail and storage integrationsMessaging integrationsQueue, issue and remote access integrationsGetting Started With AIUse the AI Assistant and AI Agent blocks while keeping workflow changes reviewable.Straight to the topic that interests you:AI Assistant promptsReviewing AI changes and billing