Share as Template

A working table is a workflow someone else can run. Share as Template packages it — columns, actions, prompts, and table logic — so it can be imported into a blank table elsewhere.

Templates are stored as JSON. Browse the ready-made ones in the template library .

What gets shared

No leads leave with the template. It is the machine, not the output.

How to share

1. Click the ⚙️ icon in the top-right of the table
2. Click Share as Template
3. Name it for the job it does — “Google Maps → verified email → Instantly”, not “Table 3”
4. Share it with your team, or submit it to the public library

Make the template usable

Whoever imports it starts with an empty table and no context.

• Name columns by output, not by provider — “Work Email”, not “Action 4”
• Leave the prompts generic. Strip your own ICP wording out of AI columns so the next person can slot theirs in.
• Note the required input. A template that expects a domain in column 1 should say so in the column name.
• Check for your own keys. Swap any bring-your-own-key action back to the Sync GTM default if you are sharing publicly.
• Test it. Import into a blank table and run five rows before you send it out.

Common use cases

• Reuse one proven workflow across several clients or brands
• Hand a build to a teammate without walking them through every column
• Publish a working workflow to the public library 
• Standardize how your team builds the same motion twice
• Keep a clean master copy of a workflow you keep modifying

Best practices

• Version the name when the workflow changes so imports stay traceable
• Keep an untouched master table and experiment in a copy
• Re-test the template after any provider action changes — an import of a broken template fails silently
• Say what input column 1 expects, in the column name itself
• Strip your own API keys and ICP-specific prompt wording before publishing

Where to next

• Templates  — the public template library
• Workspaces — where an imported template lands