Understanding Template Parameters
Template parameters are the fill-in values a Custom Agent Template asks you to supply when you apply it. They let one template work across campaigns, users, boards, and integrations without hard-coding account-specific details.
What parameters are
When you apply a template, Oktopost shows a form with one field per parameter the template author defined. Each parameter maps to a value inside the agent workflow — for example, a campaign to monitor or a board to publish to. After you submit the form, those values are written into your Draft agent.
Parameter kinds
| Kind | Description |
|---|---|
| Static | Text, number, or checkbox fields for simple values such as a keyword, threshold, or on/off toggle. |
| Entity picker | Dropdowns backed by Oktopost entities — campaign, user, board, tag, or topic. You pick from objects in your account. |
| Dropdown | A curated list of options defined by the template author, such as a fixed set of channels or categories. |
| Secret | A credential slot for integrations. The template exposes where a credential is needed without storing the credential itself. You connect the credential after apply. |
Required fields
Every parameter on a template form must be filled before you can apply the template. There are no optional parameters — if the author included a field, it is required.
Oktopost Templates and blank values
Oktopost Templates are curated for every account. When a template is promoted to the global library, entity-specific values and credentials are cleared for security. That means many Oktopost Templates start with blank entity fields and may prompt you to reconnect credentials after apply.
Why this matters
Blank values are expected — they keep account data out of shared templates. Fill every parameter and reconnect credentials before you publish the agent.Related articles
- Start a Custom Agent from a Template
- Save a Custom Agent as a Template — how template authors define parameters.
- Custom Agent Templates FAQ