13.3 Templates and Reusability

Save time by reusing proven workflows. Instead of building every taible from scratch, you can create templates that capture your best practices and share them across your organization.

Overview: Reusability in Taibles

How Reusability Works Today

Taibles provides three ways to reuse workflows:

💡 Export & Import

Export your taible structure as a .agent file and import it when starting a new project. Choose whether to include data or just the structure.

💡 Cloning

Duplicate an existing taible with one click. Perfect for creating variations of a workflow or testing changes safely.

💡 Manual Column Recreation

When you need just one column's configuration, manually recreate it in another taible by copying the settings.

Future Capabilities (Coming Soon)

Planned features to make reusability even easier:

Template Library: Browse and save templates within Taibles
Column Presets: Drag and drop pre-configured columns
Template Marketplace: Access community-contributed templates
One-Click Deployment: Instant template setup with guided configuration

These features are under development and will be released in future updates.

Part 1: Creating and Using Templates

What Is a Template?

A template is a reusable taible configuration that includes:

Column structure and types
Dependencies between columns
Run configurations
Triggers
Best practices

Use templates for:

Starting new projects quickly
Standardizing processes across your team
Sharing proven patterns
Training new team members

Creating a Template

Follow these steps to turn your taible into a reusable template:

Step 1: Build Your Master Taible

Create a complete, working taible that solves a specific use case:

💡 Example: Lead Enrichment Pipeline

Columns:

Email (manual input)
Email Validation (API check)
Company Data (enrichment)
Company Name, Size, Industry (extract from enrichment)
Lead Score (AI scoring)
Assigned To (manual selection)

Trigger: Webhook for form submissions

Testing checklist:

✅ Add test rows
✅ Verify all columns execute correctly
✅ Check error handling
✅ Validate rate limiting
✅ Test trigger if applicable

Step 2: Clean for Template Use

Before exporting, prepare your taible:

Remove Test Data

Delete all test rows so the template starts empty. Select all rows using the checkbox in the header, then right-click and choose Delete.

Document Account Requirements

Note which integration accounts are needed. Templates don't include account credentials, so users need to know which accounts to configure after import.

Add Clear Instructions

Update the taible description with setup instructions, purpose, and any special configuration notes.

Remove test data:

Select all rows (checkbox in header)
Right-click → Delete
Result: Empty taible ready for template use

Document requirements: Add a clear description to your taible that includes:

What the template does
Which integration accounts are needed
Setup instructions
Any special configuration notes

💡 Important

Templates do not include integration account credentials. Document which accounts users will need to configure after importing.

Step 3: Export as Template

Export Taible

Lead Enrichment Pipeline

Automatically enrich and score inbound leads

Include data

Export structure only (recommended for templates)

Downloaded file:

lead-enrichment-pipeline_structure-only_2024-11-19.agent

To export your taible:

Open the taible menu (three dots ⋮ on the taible card)
Click "Export"
Configure export options:
- Uncheck "Include data" (templates should be structure only)
Click "Export Taible"
File downloads as: {taible-name}_structure-only_{timestamp}.agent
Rename the file to something descriptive:
- Example: template-lead-enrichment-pipeline.agent

💡 Pro Tip

Use descriptive names like template-{use-case}-{version}.agent so your team can easily identify templates in your library.

Step 4: Store in Your Template Library

Organize templates so your team can find them:

Option 1: Shared Drive

Team Drive/
└── Taible Templates/
    ├── template-lead-enrichment-pipeline.agent
    ├── template-support-ticket-workflow.agent
    ├── template-content-approval-pipeline.agent
    └── README.md (describes each template)

Option 2: Git Repository

taible-templates/
├── lead-enrichment/
│   ├── template.agent
│   ├── README.md
│   └── screenshots/
├── support-tickets/
│   ├── template.agent
│   ├── README.md
│   └── screenshots/
└── INDEX.md (catalog of all templates)

Option 3: Internal Wiki

Create a wiki page with:

Template name and description
Download link to .agent file
Setup instructions
Screenshots
Author and last updated date

Using a Template

Once you have a template file, here's how to use it:

Step 1: Import the Template

Import Taible

📁

Click to upload or drag and drop

.agent files only

Destination Taible name

Import data

Import structure only

Import process:

Go to your Taibles page
Click "Import" button
Upload the .agent file:
- Click to browse or drag and drop
- Only .agent files are accepted
Give it a new name:
- Example: "Q4 Lead Enrichment"
- Example: "ACME Corp Leads"
Uncheck "Import data" (templates usually have no data)
Click "Import Taible"

Your new taible is created with all the column structure and configurations from the template!

Step 2: Configure Integration Accounts

Templates don't include account credentials, so you'll need to configure them:

lead_score

AI Column - Lead Scoring

OpenAI Account

Click "+" to create a new account

📝 Configuration Checklist

✅ Email Validation - No account needed

⚠️ Company Data - Clearbit account required

⚠️ Lead Score - OpenAI account required

✅ Assigned To - No account needed

For each column that needs an account:

Open the column configuration (click the gear icon ⚙️)
Find the Account selection dropdown
Select your account or click "+" to create a new one
Save the column

💡 Creating Accounts

When you click the "+" button next to an account dropdown, you can create a new integration account right from the column configuration.

Step 3: Configure Triggers (If Applicable)

If your template includes triggers:

Form Submission Webhook

Webhook Trigger

Disabled

Webhook URL

Configure this URL in your form provider (Typeform, Google Forms, etc.)

Enable Trigger

Trigger is disabled

🧪 Test Your Webhook

Send a test submission from your form to verify the webhook is working correctly.

Webhook triggers:

Open the Triggers tab
Copy the webhook URL
Configure it in your third-party service
Enable the trigger

Scheduled triggers:

Open the Triggers tab
Review the schedule
Adjust if needed
Enable the trigger

Step 4: Customize for Your Use Case

Templates are starting points—customize them to fit your needs:

Add organization-specific columns:

CRM integrations
Custom scoring logic
Internal tracking fields
Team notifications

Modify configurations:

Adjust rate limits for your plan
Update AI prompts for your domain
Change conditional logic
Add error notifications

Test thoroughly:

Add test rows
Verify all columns work
Check account connections
Test triggers

💡 Ready to Go Live

Once everything is tested and working, you're ready to use your new taible in production!

Part 2: Cloning Taibles

Sometimes you need a copy of an existing taible, not a template. Cloning is perfect for:

Creating variations of a workflow
Testing changes without affecting the original
Setting up similar workflows for different teams
Backing up a taible before major changes

How to Clone a Taible

Clone Taible

Cloning from:

Lead Enrichment Pipeline

Automatically enrich and score inbound leads

Taible name

Include data

Clone all rows from original taible

💡 Cloning creates an exact copy with all configurations. Integration accounts will work immediately since they're in the same organization.

Cloning process:

Find the taible you want to clone
Click the menu (three dots ⋮)
Select "Clone"
Configure the clone:
- Name: Pre-filled as "{Original Name} (Clone)"
- Include data: Check this to copy all rows, uncheck for structure only
Click "Clone Taible"

The cloned taible opens automatically with all configurations intact!

Clone vs. Template

💡 When to Use Each

Clone when you want an exact copy:

Same organization
Quick duplication
Testing or backup purposes
Already configured accounts work

Template when you want to share:

Different organizations
Portable across teams
Clean starting point
Requires account reconfiguration

Part 3: Example Templates

Here are some ready-to-use template examples:

Template 1: Lead Enrichment Pipeline

Lead Enrichment Pipeline

Automatically enrich and score inbound leads

Template

Column	Type	Purpose
email	Manual	Lead email address
email_validation	API	Check email validity
company_data	API	Enrich company info
company_name	Extract	Extract from enrichment
company_size	Extract	Extract employee count
industry	Extract	Extract industry
lead_score	AI	Score 0-100 based on fit
assigned_to	User Select	Manual assignment

Required Accounts

• OpenAI API (for scoring)

• Clearbit (for enrichment)

Use Cases

• Marketing qualified leads

• Event registrations

• Demo requests

Purpose: Automatically enrich and score inbound leads

Columns:

Email (manual input)
Email Validation (verify deliverability)
Company Data (enrichment API)
Company Name, Size, Industry (extract fields)
Lead Score (AI scoring 0-100)
Assigned To (user selection)

Trigger: Webhook for form submissions

Use cases:

Marketing qualified leads
Event registrations
Demo requests
Contact form submissions

Required accounts:

OpenAI API (for scoring)
Clearbit or similar (for enrichment)

Template 2: Support Ticket Workflow

Support Ticket Workflow

Process and route support tickets automatically

Template

ticket_id

Auto-generated ID

customer_email

From requester

subject

Ticket subject line

description

Full description

priority

AI detects High/Medium/Low

Template 3: Content Approval Pipeline

Content Approval Pipeline

Review and approve content before publishing

Template

1. Draft

→

2. AI Checks

→

3. Review

→

4. Publish

content_title, content_body, author, category

Manual input and metadata

seo_check, grammar_check

AI quality checks (OpenAI)

reviewer, review_status, review_notes

Human review and approval

published, publish_date

Publication tracking

Required Accounts

• OpenAI API (for SEO and grammar)

Use Cases

• Blog post approval

• Social media content

• Marketing materials

Purpose: Review and approve content before publishing

Columns:

Content Title
Content Body
Author (user selection)
Category (dropdown)
SEO Check (AI analysis)
Grammar Check (AI proofreading)
Reviewer (user selection)
Review Status (Pending/Approved/Changes Requested)
Review Notes
Published (yes/no)
Publish Date

Use cases:

Blog post approval
Social media content
Marketing materials
Documentation review

Required accounts:

OpenAI API (for SEO and grammar checks)

Part 4: Building a Column Pattern Library

While Taibles doesn't yet have a column preset system, you can maintain your own pattern library:

Documenting Reusable Patterns

Create internal documentation for frequently used column configurations:

Email Validation

Custom Code

Output Type

Map (valid, reason)

Dependencies

email column

Run Mode

Once when dependencies change

Rate Limit

None (local)

Use When:

Any taible collecting email addresses

Lead Scoring

AI Column

Output Type

Number (0-100)

Account

OpenAI API

Dependencies

company_size, industry, job_title

Model

GPT-4

Prompt Template:

Score this lead from 0-100 based on fit. Company Size: [Company Size]. Industry: [Industry]. Job Title: [Job Title]. Scoring criteria: Enterprise (1000+): +30. Target industries (SaaS, Tech): +20. Decision makers: +30. Return only the number.

Use When:

Qualifying leads for sales prioritization

Company Enrichment

API Integration

Output Type

JSON Object

Account

Clearbit API

Dependencies

email or domain

Rate Limit

600 requests/hour

Error Handling:

Skip if company not found (404). Retry on server errors (5xx).

Use When:

Enriching B2B leads or contacts with company data

Pattern: Email Validation

Type: Custom Code Output: Map (valid: true/false, reason: string) Purpose: Validate email format and check for disposable domains

Configuration:

Dependencies: email column
Run Mode: Once when dependencies change
Rate Limit: None (local validation)

Use when: Any taible collecting email addresses

Pattern: Lead Scoring

Type: AI Column Output: Number (0-100) Purpose: Score leads based on fit

Configuration:

Dependencies: company_size, industry, job_title
Account: OpenAI API
Model: GPT-4
Prompt: "Score this lead from 0-100 based on fit. Company Size: [Company Size]. Industry: [Industry]. Job Title: [Job Title]. Scoring criteria: Enterprise companies (1000+ employees): +30. Target industries (SaaS, Tech): +20. Decision maker titles: +30. Return only the number."

Use when: Qualifying leads for sales

Pattern: Company Enrichment

Type: API Integration Output: JSON object with company data Purpose: Enrich company information from email or domain

Configuration:

Dependencies: email or domain column
Account: Clearbit API
Method: Company Lookup
Rate Limit: 600 requests/hour
Error Handling: Skip if company not found

Use when: Enriching B2B leads or contacts

Quick Reference Method

For complex patterns:

Configure perfectly once in a taible
Take screenshots of all configuration tabs
Export the taible as reference

Store in your pattern library:

Column Library/
├── email-validation/
│   ├── config-screenshot.png
│   ├── code.txt
│   └── README.md
├── lead-scoring/
│   ├── config-screenshot.png
│   ├── prompt.txt
│   └── README.md
└── company-enrichment/
    ├── config-screenshot.png
    └── README.md

Reference when creating similar columns

Part 5: Best Practices

Practice 1: Start with Templates

💡 ✅ Do This

Need lead enrichment?

Check template library
Find "Lead Enrichment Pipeline"
Import template
Customize for your needs

Time: 30 minutes Result: Built on proven pattern

💡 ❌ Not This

Need lead enrichment?

Build from scratch
Figure out best practices
Test and iterate

Time: 3 hours Result: Might miss best practices

Practice 2: Build Generic, Customize Specific

❌

Too Specific

Column: acme_corp_lead_score

"Score for ACME Corp based on our Q4 2024 criteria..."

Problems:

• Only works for ACME Corp
• Only valid for Q4 2024
• Can't be reused elsewhere
• Requires complete rebuild for other teams

✅

Just Right

Column: lead_score

"Score lead from 0-100 based on: Company Size: [Company Size]. Industry: [Industry]. Job Title: [Job Title]. Return only the number."

Benefits:

• Works for any company
• Valid any time
• Easy to customize if needed
• Covers 80% of use cases

Templates should work for 80% of use cases with minimal changes.

Too specific:

Column: acme_corp_lead_score
Prompt: "Score for ACME Corp based on Q4 2024 criteria..."

→ Only works for ACME Corp in Q4

Just right:

Column: lead_score
Prompt: "Score lead from 0-100 based on: Company Size: [Company Size]. Industry: [Industry]. Job Title: [Job Title]. Return only the number."

→ Works for any company, any time → Users customize per instance if needed

Practice 3: Document Everything

Every template should include:

Template: Lead Enrichment Pipeline

Purpose:

Automatically enrich and score inbound leads from forms.

Required Accounts:

• OpenAI API (for lead scoring)
• Clearbit API (for company enrichment)

Setup Instructions:

1. Import template
2. Configure OpenAI account in "lead_score" column
3. Configure Clearbit account in "company_data" column
4. Set webhook URL in trigger
5. Test with sample lead
6. Enable trigger when ready

Customization Ideas:

• Adjust lead scoring criteria in prompt
• Add CRM integration columns
• Modify rate limits for your plan

Support: sarah@company.com

Last Updated: 2024-11-19

In the taible description:

Template: Lead Enrichment Pipeline

Purpose:
Automatically enrich and score inbound leads from forms.

Required Accounts:
- OpenAI API (for lead scoring)
- Clearbit API (for company enrichment)

Setup Instructions:
1. Import template
2. Configure OpenAI account in "lead_score" column
3. Configure Clearbit account in "company_data" column
4. Set webhook URL in trigger
5. Test with sample lead
6. Enable trigger when ready

Customization Ideas:
- Adjust lead scoring criteria in prompt
- Add CRM integration columns
- Modify rate limits for your plan

Support: sarah@company.com
Last Updated: 2024-11-19

In your template library README:

Template name and purpose
What it solves
Required accounts
Typical use cases
Setup time estimate
Difficulty level

Practice 4: Version Your Templates

Track template evolution over time:

Template Library/

└── lead-enrichment/

├── v1.0-basic-enrichment.agent

├── v2.0-added-scoring.agent

├── v3.0-added-validation.agent

├── v3.1-improved-prompts.agentLatest

└── CHANGELOG.md

CHANGELOG.md

v3.1

2024-11-19

Current

• Improved lead scoring prompt for accuracy
• Added email validation before enrichment
• Updated rate limits for new API tiers

v3.0

2024-11-15

• Added email validation column
• Added conditional execution to skip invalid emails

v2.0

2024-11-01

• Added AI lead scoring column
• Added user assignment column

v1.0

2024-10-15

• Initial template with basic enrichment

Directory structure:

Template Library/
└── lead-enrichment/
    ├── v1.0-basic-enrichment.agent
    ├── v2.0-added-scoring.agent
    ├── v3.0-added-validation.agent
    ├── v3.1-improved-prompts.agent  ← Latest
    └── CHANGELOG.md

CHANGELOG.md example:

markdown

# Lead Enrichment Template Changelog

## v3.1 (2024-11-19)
- Improved lead scoring prompt for accuracy
- Added email validation before enrichment
- Updated rate limits for new API tiers

## v3.0 (2024-11-15)
- Added email validation column
- Added conditional execution to skip invalid emails

## v2.0 (2024-11-01)
- Added AI lead scoring column
- Added user assignment column

## v1.0 (2024-10-15)
- Initial template with basic enrichment

Make templates easy to discover:

Taible Template Library

Browse our proven taible templates

🎯

Lead Enrichment Pipeline

v3.1

Enrich and score inbound leads automatically

Used by: Sales, Marketing

🎫

Support Ticket Workflow

v2.0

Route and manage support tickets with AI

Used by: Customer Success, IT

📝

Content Approval Pipeline

v1.5

Review and approve content before publishing

Used by: Marketing, Communications

Contributing

Have a great taible? Share it as a template!

Create an internal wiki page:

Taible Template Library
=======================

Browse our proven taible templates:

🎯 Lead Enrichment Pipeline v3.1
   Enrich and score inbound leads
   Used by: Sales, Marketing
   [Download] [Setup Guide]

🎫 Support Ticket Workflow v2.0
   Route and manage support tickets
   Used by: Customer Success, IT
   [Download] [Setup Guide]

📝 Content Approval Pipeline v1.5
   Review and approve content
   Used by: Marketing, Communications
   [Download] [Setup Guide]

Contributing:
Have a great taible? Share it as a template!
[Contribution Guidelines]

Benefits:

Everyone saves time
Consistency across teams
New team members onboard faster
Best practices spread naturally

Practice 6: Keep Templates Updated

Quarterly Review Checklist

📢

Template Update Announcement

Template Update: Lead Enrichment v3.2

What's new:

• Now uses GPT-4 for better scoring accuracy
• Added Slack notification for high-score leads
• Reduced API costs by 40%
• Updated setup documentation

Download|Migration Guide

Quarterly review checklist:

✅ Test all templates (do they still work?)
✅ Update for new features
✅ Incorporate user feedback
✅ Update documentation and screenshots
✅ Increment version numbers
✅ Announce updates to your team

Update announcement example:

📢 Template Update: Lead Enrichment v3.2

What's new:
- Now uses GPT-4 for better scoring accuracy
- Added Slack notification for high-score leads
- Reduced API costs by 40%
- Updated setup documentation

Download: [link]
Migration Guide: [link]

Part 6: Real-World Template Library

Here's how an organization might structure their templates:

Taible Templates/

├── Sales & Marketing/

│ ├── lead-enrichment-pipeline/

│ ├── outbound-prospecting/

│ ├── event-follow-up/

│ └── campaign-tracking/

├── Customer Success/

│ ├── support-ticket-workflow/

│ ├── onboarding-checklist/

│ ├── churn-prediction/

│ └── nps-survey-processing/

├── Operations/

│ ├── invoice-processing/

│ ├── expense-approval/

│ ├── vendor-onboarding/

│ └── inventory-tracking/

└── Content & Marketing/

├── content-approval-pipeline/

├── social-media-scheduler/

├── seo-analysis/

└── newsletter-automation/

Each folder contains:

📄

template.agent file

📖

README.md

📸

screenshots/ folder

📝

CHANGELOG.md

Result:

Your team moves fast, builds on proven patterns, and maintains consistency across all workflows.

Taible Templates/
├── Sales & Marketing/
│   ├── lead-enrichment-pipeline/
│   ├── outbound-prospecting/
│   ├── event-follow-up/
│   └── campaign-tracking/
├── Customer Success/
│   ├── support-ticket-workflow/
│   ├── onboarding-checklist/
│   ├── churn-prediction/
│   └── nps-survey-processing/
├── Operations/
│   ├── invoice-processing/
│   ├── expense-approval/
│   ├── vendor-onboarding/
│   └── inventory-tracking/
└── Content & Marketing/
    ├── content-approval-pipeline/
    ├── social-media-scheduler/
    ├── seo-analysis/
    └── newsletter-automation/

Each folder contains:

template.agent file
README.md with setup instructions
screenshots/ folder
CHANGELOG.md for version history

Result: Your team moves fast, builds on proven patterns, and maintains consistency across all workflows.

Summary

You now know how to create and use templates for maximum reusability:

✅ Creating Templates:

Build and test complete taibles
Remove test data and clean for reuse
Export structure only (no data)
Store in shared library with documentation

✅ Using Templates:

Import from library
Reconfigure integration accounts
Customize for specific needs
Test before going live

✅ Cloning:

Quick duplication for testing or variations
Choose whether to include data
Perfect for same-organization use

✅ Best Practices:

Start with templates (save 80% of setup time)
Build generic, customize specific
Document everything (purpose, requirements, setup)
Version templates (track improvements)
Share across organization (wiki or shared drive)
Keep templates updated (quarterly reviews)

✅ Pattern Library:

Document reusable column configurations
Screenshot complex setups
Create quick reference guides
Share common patterns

Next Steps

Chapter 14: Real-World Automation Examples explores complete, production-ready automation examples across different industries and use cases.

Let's see Taibles in action with real-world examples! 🚀

13.3 Templates and Reusability ​

Overview: Reusability in Taibles ​

How Reusability Works Today ​

💡 Export & Import

💡 Cloning

💡 Manual Column Recreation

Future Capabilities (Coming Soon) ​

Part 1: Creating and Using Templates ​

What Is a Template? ​

Creating a Template ​

Step 1: Build Your Master Taible ​

💡 Example: Lead Enrichment Pipeline

Step 2: Clean for Template Use ​

Remove Test Data

Document Account Requirements

Add Clear Instructions

💡 Important

Step 3: Export as Template ​

Export Taible

💡 Pro Tip

Step 4: Store in Your Template Library ​

Using a Template ​

Step 1: Import the Template ​

Import Taible

Step 2: Configure Integration Accounts ​

💡 Creating Accounts

Step 3: Configure Triggers (If Applicable) ​

Step 4: Customize for Your Use Case ​

💡 Ready to Go Live

Part 2: Cloning Taibles ​

How to Clone a Taible ​

Clone Taible

Clone vs. Template ​

💡 When to Use Each

Part 3: Example Templates ​

Template 1: Lead Enrichment Pipeline ​

Template 2: Support Ticket Workflow ​

Template 3: Content Approval Pipeline ​

Part 4: Building a Column Pattern Library ​

Documenting Reusable Patterns ​

Quick Reference Method ​

Part 5: Best Practices ​

Practice 1: Start with Templates ​

💡 ✅ Do This

💡 ❌ Not This

Practice 2: Build Generic, Customize Specific ​

Practice 3: Document Everything ​

Practice 4: Version Your Templates ​

Practice 5: Share Across Your Organization ​

Taible Template Library

Practice 6: Keep Templates Updated ​

Part 6: Real-World Template Library ​

Summary ​

Next Steps ​

13.3 Templates and Reusability

Overview: Reusability in Taibles

How Reusability Works Today

Future Capabilities (Coming Soon)

Part 1: Creating and Using Templates

What Is a Template?

Creating a Template

Step 1: Build Your Master Taible

Step 2: Clean for Template Use

Step 3: Export as Template

Step 4: Store in Your Template Library

Using a Template

Step 1: Import the Template

Step 2: Configure Integration Accounts

Step 3: Configure Triggers (If Applicable)

Step 4: Customize for Your Use Case

Part 2: Cloning Taibles

How to Clone a Taible

Clone vs. Template

Part 3: Example Templates

Template 1: Lead Enrichment Pipeline

Template 2: Support Ticket Workflow

Template 3: Content Approval Pipeline

Part 4: Building a Column Pattern Library

Documenting Reusable Patterns

Quick Reference Method

Part 5: Best Practices

Practice 1: Start with Templates

Practice 2: Build Generic, Customize Specific

Practice 3: Document Everything

Practice 4: Version Your Templates

Practice 5: Share Across Your Organization

Practice 6: Keep Templates Updated

Part 6: Real-World Template Library

Summary

Next Steps