Templates Overview

What are templates?

Templates are saved snapshots of workflows, tables, or rows that can be shared across your workspace or made public for anyone to use. They let you package up a working automation or data structure and deploy it again — cleanly, with no copy-paste, no broken references. When you instantiate a template, Connie creates a fully independent copy. All internal IDs are remapped to fresh values, so the new instance has no link to the original. You can modify it freely without affecting the source template or anyone else using it.

Template types

There are three types of templates, matching the three main building blocks in Connie:

Workflow

A complete automation — triggers, nodes, edges, and configuration — ready to run.

Table

A table schema with columns, types, and optional pre-filled rows.

Row

A single row configuration, useful for seeding tables with standardised records.

Templates can be private to your workspace or marked public to share with all Connie users. Public templates appear in the template gallery and can be instantiated by anyone.

Listing templates

GET /api/v2/templates

Returns all templates visible to your workspace — both templates created in your workspace and any public templates. Filter by type to narrow results:

GET /api/v2/templates?type=workflow
GET /api/v2/templates?type=table
GET /api/v2/templates?type=row

Creating a template

POST /api/v2/templates

Turn any existing workflow or table into a template by passing its ID:

{
  "type": "workflow",
  "source_id": "3f2e1d4c-...",
  "name": "LinkedIn outreach sequence",
  "description": "5-step sequence that enriches a lead, drafts a message, and sends via LinkedIn.",
  "is_public": false
}

Creating templates requires owner, admin, or developer role in your workspace.

The source workflow or table is not modified — a template is a snapshot taken at the moment of creation. Changes you make to the source after that point are not reflected in the template.

Instantiating a template

POST /api/v2/templates/{templateId}/instantiate

This is where the magic happens. Instantiating a template:

Creates a new table in your workspace
Remaps all workflow node and edge IDs to fresh UUIDs
Returns the new table entity and the remapped workflow graph

{
  "name": "Q3 outreach campaign",
  "workspace_id": "your-workspace-uuid"
}

The response includes both objects:

{
  "table": {
    "id": "new-table-uuid",
    "name": "Q3 outreach campaign",
    "workspace_id": "..."
  },
  "graph": {
    "nodes": [...],
    "edges": [...]
  }
}

The graph is returned but not yet persisted. You must make one additional call to save it:

PUT /api/workflows/{tableId}/graph

with the graph object from the response. This two-step design lets you inspect or modify the graph before committing it.

App templates

App templates are curated by the Connie team — pre-built integrations and use-case starters that cover common GTM motions out of the box.

GET /api/apps/templates
GET /api/apps/templates?category=outreach

These are read-only. You can instantiate them but not modify the source. Think of them as the official template library.

Skill templates

Skill templates are reusable AI skill configurations that you can load into the AI Brain.

GET /api/skills/templates
GET /api/skills/templates?category=research

Skill templates are curated for specific AI-driven tasks — lead research, email drafting, data summarisation, and more. Browse and instantiate them to give Connie pre-configured capabilities without building from scratch.

Common patterns

Build and test a workflow in your workspace
POST /api/v2/templates with is_public: false — private to your workspace
Share the template ID with teammates
Each teammate calls POST /api/v2/templates/{id}/instantiate to get their own independent copy

Publish a workflow for the community

Same as above but with is_public: true. The template appears in the public gallery and anyone can instantiate it.

Seed a new workspace with standard tables

Create table templates for your core data structures (contacts, companies, deals). When onboarding a new workspace, instantiate all of them in sequence to get a consistent starting layout in seconds.

API reference

List templates

Browse workspace and public templates

Create template

Save a workflow or table as a template

Instantiate

Deploy a template into a new independent copy

App templates

Browse curated starter templates

​What are templates?

​Template types

Workflow

Table

Row

​Listing templates

​Creating a template

​Instantiating a template

​App templates

​Skill templates

​Common patterns

​Share a workflow with your team

​Publish a workflow for the community

​Seed a new workspace with standard tables

​API reference

List templates

Create template

Instantiate

App templates

What are templates?

Template types

Listing templates

Creating a template

Instantiating a template

App templates

Skill templates

Common patterns

Share a workflow with your team

Publish a workflow for the community

Seed a new workspace with standard tables

API reference