> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connie.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Templates Overview

> Save, share, and reuse workflows and tables so your team isn't starting from scratch every time.

## 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:

<CardGroup cols={3}>
  <Card title="Workflow" icon="diagram-project">
    A complete automation — triggers, nodes, edges, and configuration — ready to run.
  </Card>

  <Card title="Table" icon="table">
    A table schema with columns, types, and optional pre-filled rows.
  </Card>

  <Card title="Row" icon="list">
    A single row configuration, useful for seeding tables with standardised records.
  </Card>
</CardGroup>

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:

```json theme={null}
{
  "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
}
```

<Note>
  Creating templates requires **owner, admin, or developer** role in your workspace.
</Note>

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:

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

```json theme={null}
{
  "name": "Q3 outreach campaign",
  "workspace_id": "your-workspace-uuid"
}
```

The response includes both objects:

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

<Warning>
  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.
</Warning>

***

## 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

### Share a workflow with your team

1. Build and test a workflow in your workspace
2. `POST /api/v2/templates` with `is_public: false` — private to your workspace
3. Share the template ID with teammates
4. 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

<CardGroup cols={2}>
  <Card title="List templates" icon="list" href="/api-reference/templates/list-templates">
    Browse workspace and public templates
  </Card>

  <Card title="Create template" icon="plus" href="/api-reference/templates/create-template">
    Save a workflow or table as a template
  </Card>

  <Card title="Instantiate" icon="copy" href="/api-reference/templates/instantiate-template">
    Deploy a template into a new independent copy
  </Card>

  <Card title="App templates" icon="store" href="/api-reference/templates/list-app-templates">
    Browse curated starter templates
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.