Start in the builder
Open Sample Data, select the JSON editor, and provide an object matching the placeholders:{{user.name}}, test an each container over items, and change status to exercise each conditional branch.
Reusable sets and template samples
The Sample Data area manages named datasets; a template version also stores the sample data used with its content. When loading a reusable set into the editor, verify the actual data shown in the current template before saving. Do not assume editing a library dataset updates every saved template version. An entity defines a reusable object shape so you can build multiple templates around the same service data. For example, customer-created and customer-updated templates can share a Stripe Customer entity; each template’s sample data supplies values for that shape. In the builder, select an entity under Entity Data to generate starter sample values, then use JSON Editor to replace them with representative values. Selecting an entity replaces the current sample data, so preserve useful test cases first. You can also supply JSON directly without defining an entity.Test cases to keep
Use synthetic names, emails, and URLs. Community/shared sample data can be visible to other users; never include credentials or real customer records.
Move data between tools
Copy the JSON from the editor into a local fixture or paste a fixture into a new dataset. Keep data separate from the outer API send body:template_id and destination belong beside data, not inside it.
Before deleting a dataset, preserve examples you need and review its usage. For an integration, read GET /v1/templates/{id}/input-schema and validate the actual incoming data; a sample is not a schema validator.
Placeholders · Limits