Your Make workflow. Your next image.
A new article, product or spreadsheet row can become a visual asset. Make sends the data; your Pikstrapi template gives it a design.
Connect through HTTP and webhooks. One Pikstrapi account for your designs and API.
New content → reusable designfor great
ideas.
Keep the design. Change the content.
Create one reusable template for your blog covers, product images or course certificates. You decide which data changes each time.
- Save a single-page template and give its text layer the unique name title.
- In your account’s API playground, copy the template UUID, endpoint and API key. The template and key must belong to the same account.
- Choose a Make trigger that supplies a title and a source record ID. Start with one sample record before connecting a batch.
Configure HTTP → Make a request.
Use the endpoint from your API playground. YOUR_API_BASE_URL represents your full API base including /api/v1; replace it if shown below.
POST https://api.pikstrapi.com/api/v1/templates/generate-image- Authentication type: API key. Create Credentials with your full Pikstrapi key, placement In the header and parameter name x-api-key. No Bearer prefix is needed.
- Method: POST. Choose Body content type application/JSON and Body input method Data structure.
- Create the structure from this example. Replace templateId and webhookUrl; map the source title to layers → title → text and its ID to metadata → sourceId. A data structure escapes quotation marks and line breaks.
- Parse response: Yes. Run one record and inspect jobId. Turn on HTTP error handling so failed requests stop the scenario.
{
"templateId": "YOUR_TEMPLATE_ID",
"exportFormat": "png",
"mode": "deferred",
"layers": {
"title": {
"text": "A new article. Ready to share."
}
},
"webhookUrl": "YOUR_MAKE_WEBHOOK_URL",
"metadata": {
"sourceId": "YOUR_SOURCE_RECORD_ID"
}
}Replace every placeholder with your own values. The saved layer name is title; the request changes its text.
A job first. The finished image next.
Deferred rendering returns HTTP 200 with jobId, status, progress and fileId. That response acknowledges the request. The finished file arrives separately.
Immediate mode returns the binary file instead of JSON. This guide uses deferred mode so the receiver can handle completion without waiting for image bytes.
- Create a second scenario with Webhooks → Custom webhook. Copy its URL into webhookUrl in the sending scenario. Use Run once to capture a sample, then enable the receiver.
- Continue only when event equals render.completed. Match data.metadata.sourceId to your original record and read data.fileUrl. Handle render.failed separately.
- If your next app needs a file, use HTTP → Download a file with the returned URL and map the resulting file into the upload module.
Check the file’s access rules before handing its URL to another service. For private storage, download with the required credentials and deliver through your own destination. Deduplicate repeated deliveries using jobId and event.
Know what your automation needs.
Your automation service and Pikstrapi have separate usage allowances. One source record can run several steps; it is not necessarily one automation credit or task.
Make Free lists 1,000 credits per month, two active scenarios, a 15-minute minimum scheduled interval and a 5 MB file limit. Instant webhooks are separate from scheduled polling. This two-scenario setup can use both available scenario slots.
Configuration checked against the Pikstrapi API contract and official documentation on 9 October 2026. Verify with your own account before enabling the workflow.
Start with one record. Make it yours.
A title with quotation marks, a long headline and a missing field are useful first tests. Review the image and the receiving record before enabling a batch.
Make is a separate service. This guide uses its HTTP and webhook tools; it does not describe a native Pikstrapi connector or a commercial partnership.