Skip to main content

Supported Resources

[API Docs]

Blueprints support the following resource types. Each resource type corresponds to a ResourceNodeType in the Blueprint Manifest API.

Resource Types​

Resource TypeAPI ValueDescription
JourneysjourneyJourney configurations and launchers
Design BuilderdesignbuilderJourney design / theming configurations
ProductsproductProduct entities
PricespricePrice entities
CouponscouponPromotional codes
Product Recommendationsproduct_recommendationCross-sellable product configurations
TaxestaxTax configurations
FilesfileImages, document templates, attachments, downloads
Email TemplatesemailtemplateEmail templates with attachments and variables
SchemasschemaFull entity schemas
Schema Attributesschema_attributeIndividual schema attributes
Schema Capabilitiesschema_capabilitySchema capabilities
Schema Groupsschema_groupAttribute groups
Schema Group Headlinesschema_group_headlineGroup headlines
Automation Flowsautomation_flowAutomation flow configurations
Entity Mappingsentity_mappingEntity mapping definitions
Workflow Definitionsworkflow_definitionWorkflow configurations
Closing Reasonsclosing_reasonWorkflow closing reasons
TaxonomiestaxonomyTaxonomy definitions
Taxonomy Classificationstaxonomy_classificationPurposes and labels
WebhookswebhookWebhook configurations
IntegrationsintegrationERP and third-party integrations
Custom Variablescustom_variableCustom template variables
DashboardsdashboardDashboard configurations
Saved Viewssaved_viewTable and inbox saved views
RolesroleRoles and permission configurations
User GroupsusergroupUser group definitions
Portal Configurationsportal_configCustomer portal configurations
AppsappApp configurations
TargetstargetTarget / goal definitions
Kanban ViewskanbanKanban board configurations
Validation Rulesvalidation_ruleEntity validation rules
Flow Templatesflow_templateReusable flow templates
Notification Templatesnotification_templateNotification template configurations

Known Limitations​

  1. Webhooks are included as part of automations but created in an incomplete state -- users must manually add the URL and auth configuration after import.
  2. Designs can be copied standalone, but the target organization's default design is applied for imported journeys.
  3. Schema capabilities are only exported when exporting the full schema (not as individual resourcesMove).

See Also​