Intake Templates

Overview

Templates let you save item sets and reuse them across projects. Instead of defining items from scratch each time, point define_intake at a template and the items are filled in automatically. You can still override or extend template items for a specific project.

Templates are especially useful in agency settings where you run the same type of project repeatedly — restaurant websites, advisor pages, e-commerce stores — and want a consistent, tested item set.

Built-in templates

Three public templates are available on all plans, including Free. They are always present and cannot be deleted.

`web-restaurant`

For restaurant and cafe website projects.

Item key	Type	Notes
`logo`	image	SVG or PNG, transparent background
`hero_copy`	longtext	Main headline and subheadline
`menu_pdf`	file	Current menu in PDF format
`opening_hours`	structured	Object with `mon_fri`, `sat`, `sun` fields
`photos`	file_list	Food/ambiance photography
`social_links`	url	Instagram, Facebook, etc.
`booking_url`	url	Optional — reservation link

`web-advisor`

For financial advisors, coaches, consultants, and similar professional profile pages.

Item key	Type	Notes
`headshot`	image	Professional photo
`bio`	longtext	About the advisor
`services`	longtext	Services offered
`calendly_url`	url	Optional — booking link
`linkedin_url`	url	Optional — LinkedIn profile
`logo`	image	Optional — firm logo

`web-ecommerce`

For online stores being built or migrated.

Item key	Type	Notes
`logo`	image	Brand logo
`brand_colors`	color_list	Primary and secondary brand colors
`product_descriptions`	longtext	Catalog copy
`existing_products_csv`	file	Optional — product export from current platform
`stripe_keys`	secret	Stripe publishable + secret key
`shipping_zones`	structured	Delivery regions and rates

Using a template in define_intake

Pass the template slug in the template field:

json

{
  "project_name": "Bella Cucina Restaurant Website",
  "client": {
    "email": "[email protected]",
    "name": "Marco"
  },
  "template": "web-restaurant",
  "branding": {
    "sender_name": "Radim"
  }
}

This creates an intake with all web-restaurant items pre-populated.

Overriding and extending

Provide an items array alongside template to override specific items or add new ones. Items in your items array are merged with the template:

If key matches a template item, your definition overrides the template's
If key is new, it is appended after the template items

json

{
  "template": "web-restaurant",
  "items": [
    {
      "key": "menu_pdf",
      "required": false,
      "help": "Only needed if you want a downloadable menu link. Skip if menu is managed online."
    },
    {
      "key": "allergen_info",
      "type": "file",
      "label": "Allergen information document",
      "required": false
    }
  ]
}

Creating custom templates

From scratch

POST /v1/templates

json

{
  "name": "SaaS Landing Page",
  "slug": "saas-landing",
  "description": "Standard intake for SaaS product landing page projects",
  "language": "en",
  "items": [
    {"key": "logo", "type": "image", "label": "Product logo"},
    {"key": "hero_headline", "type": "text", "label": "Hero headline", "max_chars": 80},
    {"key": "hero_subline", "type": "text", "label": "Hero subline", "max_chars": 160},
    {"key": "stripe_keys", "type": "secret", "label": "Stripe API keys"}
  ]
}

From an existing intake

If you already have an intake whose items represent a workflow you want to repeat:

POST /v1/templates

json

{
  "from_intake_id": "int_01J3K...",
  "name": "My Standard Restaurant Intake",
  "slug": "my-restaurant"
}

BriefGate copies the item definitions (not the submitted values) into a new template.

Listing templates

GET /v1/templates

Returns public templates and your own custom templates. Filter for public only:

GET /v1/templates?public=true

Response includes slug, name, description, items_count, created_by, and is_public.

Agency: team-shared templates

On Agency plans, templates created by any seat member are visible to all seats in the account. There is no separate sharing step — templates are team-scoped by default.

This lets you build a library of standard intake checklists once and use them across all projects, regardless of which team member creates the intake.

To keep templates organized, use consistent slug naming:

web-restaurant-v2
web-advisor-minimal
webapp-onboarding

Custom templates on Free and Solo plans are scoped to the account's single seat.