Templates

What Are Templates

Templates are pre-configured notebooks designed for common workflows. Instead of starting from scratch, you clone a template and customize it for your specific needs.

Each template includes:

• •Pre-written blocks with proven prompt structures
• •Recommended integrations for that workflow
• •Guidance on how to adapt it

Finding Templates

Browse templates in the Template Gallery. They're organized by category — productivity, sales, research, reporting — and tagged by the integrations they use.

When you find one that fits, click Use Template. Deep Notebook creates a copy in your account that you can modify freely. Your changes don't affect the original template.

Using a Template

After cloning, review the blocks. Templates include placeholder instructions that you'll want to customize:

• •Replace generic references with your specific sources ("the #general channel" → "the #product-updates channel")
• •Adjust filters to match your criteria ("emails from last week" → "emails from investors this month")
• •Change output formats if needed

Then connect the required integrations. The template tells you what it needs — Gmail and Slack, for example. Enable those in the notebook's Integrations panel.

Run each block to test. Adjust instructions until the output matches what you need.

Creating Your Own Templates

Built a workflow worth reusing? You can save any notebook as a template.

Click Notebook Menu → Save as Template. Add a title, description, and tags. Specify which integrations are required. Your template appears in your personal library.

Sharing Templates

Templates can be private (only you) or shared:

• •Private — Visible only in your account
• •Team — Shared with members of your workspace
• •Public — Submitted to the Template Gallery for all users

To share publicly, your template goes through a brief review to ensure quality and clarity.

Template Best Practices

Good templates share characteristics:

Clear instructions — Prompts should be specific enough to work but generic enough to adapt. "Find emails from [your target domain]" is more reusable than "Find emails from acme.com."

Logical structure — Blocks should flow naturally. Early blocks gather information; later blocks synthesize and output.

Documented requirements — Note which integrations are necessary and what permissions they need.

Tested thoroughly — Run the workflow multiple times before sharing. Edge cases reveal fragile prompts.