Skip to main content
Use a separate template for experiments that should not affect an existing integration’s current version.

​
Duplicate a template

From Templates, use the template’s duplicate action and give the copy a distinct name. Verify its sample data, version state, destination references, and modal actions before sending. A copied template has a different ID; update integrations only when you intend them to use it.

​
Import and export

The builder’s JSON view exposes message JSON. Save the JSON together with synthetic sample data when keeping a reviewable example outside the app. Distinguish the LithoBlocks template format from the compiled Slack output: compile expands directives and resolves data, so its output does not preserve the original authoring structure. When importing JSON, inspect the parsed blocks, restore required sample data, and validate every interactive action. Do not assume arbitrary Slack Block Kit JSON is a lossless LithoBlocks template import or that exported IDs and webhook references will work in a different organization.

​
Community templates

Browse Community Templates, inspect the example and its data, and copy the template into your organization before adapting it. Community examples are starting points; verify destinations, permissions, and content before using them. When publishing through the community controls, review the complete template and sample data for private information. Publishing makes the shared content available to other users. Removing a public listing does not retract copies other users have already made.

​
Retire a template

Find API callers, schedules, digests, and other dependencies before deleting a template. Pause or migrate those workflows first. Old Slack messages retain their original action configuration, but deleting a referenced destination or modal can still break future interactions. Versioning · Components · Security and data