Uploading your own templates
Publish reusable workflows to prove capability and attract hire requests that come pre-scoped.
A template is the most efficient marketing an expert on this platform can do. It demonstrates capability in a form a client can actually inspect, and hire requests that start from one arrive pre-scoped — the client is asking for a known thing rather than describing a vague one.
Visibility
| Setting | Who sees it | Where hire requests go |
|---|---|---|
| Public | Everyone in the library | The open board, or directly to you if the client chooses |
| Owner-only | Hidden from the library | Privately to you — nobody else can respond |
Before you publish
- Strip credentials, tokens, endpoints, and customer data from the export. This is the mistake to care about — a template is a file other people read.
- Describe what it does in business terms, and name the platform and the apps it touches.
- Say what a buyer still has to supply: accounts, API keys, field mappings.
- Give it an honest complexity level. An over-sold template generates hire requests you then have to talk down.
Check the export for secrets
Workflow exports frequently contain credential references, internal URLs, and sample records from real systems. Open the file and read it before uploading.
You can edit or remove your templates at any time — unless a template has active work tied to it, in which case it is locked until that work finishes so the record of what was hired stays intact.
34 articles · Ask a question