Direct answer: Contentful models content, Pixelixe generates the share image
Contentful social image automation works by mapping entry fields such as title, content type, locale, author, image asset, product, or release label into a Pixelixe template. Pixelixe returns a generated image URL that can be attached to the entry, route metadata, or publishing workflow.
Use Contentful for structured content, localization, publishing status, and content models.
Use Pixelixe for repeatable social image rendering from approved templates.
Use publish webhooks, serverless functions, queues, or automation platforms to generate and store image URLs.
Contentful social image workflow map
Map content model fields to template layers so each entry gets a consistent but unique visual.
| Contentful object | Pixelixe mapping | Output |
|---|
| Entry title | Headline layer | A unique social image headline for each entry. |
|---|
| Content type | Badge or template choice | Different templates for blog posts, docs, changelogs, case studies, or launches. |
|---|
| Asset field | Image layer | Cover image, screenshot, product image, or speaker photo. |
|---|
| Locale | Text and variant fields | Localized social cards for translated entries. |
|---|
| Publish event | Render trigger | Generate or refresh the image when content changes. |
|---|
Contentful publish webhook to Pixelixe payload
Use this payload shape inside a webhook handler, serverless function, queue worker, or automation tool.
API request
POST https://studio.pixelixe.com/api/graphic/automation/v2
Content-Type: application/json
{
"document_uid": "contentful_social_template_uid",
"api_key": "YOUR_API_KEY",
"format": "json",
"image_type": "png",
"modifications": [
{ "element_name": "title", "type": "text", "text": "{{entry.fields.title}}" },
{ "element_name": "type", "type": "text", "text": "{{entry.sys.contentType}}" },
{ "element_name": "cover", "type": "image", "image_url": "{{entry.fields.coverImage.url}}" },
{ "element_name": "locale", "type": "text", "text": "{{entry.sys.locale}}" }
]
}
Generated output
{
"status": "success",
"image_url": "https://studio.pixelixe.com/storage/file/.../contentful-social-image.png"
}
For localized entries, generate one image per locale and store the returned URL in the corresponding locale field or route metadata system.
Contentful image automations with high ROI
These workflows reinforce topical authority because they connect CMS publishing, social previews, and dynamic image generation.
Blog and resource social cards
Render branded images for every new article, guide, comparison page, and template page.
Docs and changelog previews
Generate launch cards, release notes graphics, and documentation share images from content fields.
Localized market visuals
Create locale-specific images from translated entry fields while keeping one visual system.
Programmatic page images
Support many routes where content type, industry, location, product, or offer fields change.
Contentful implementation workflow
Keep the content model stable and let Pixelixe handle the visual rendering.
Choose content types
Start with blog posts, docs pages, changelog entries, case studies, launches, or resource pages.
Create image templates
Use one template per content type or one flexible template with content-type badges.
Trigger on publish
Call Pixelixe from a webhook handler, serverless function, queue, or automation scenario.
Store the image URL
Attach the returned URL to the entry, route metadata, static build, or publishing workflow.
Related Pixelixe workflows
Use these connected pages to evaluate the implementation path, adjacent use cases, and Pixelixe product fit.
