Direct answer: Airtable stores the records, Pixelixe renders the branded image
Airtable is a strong source of structured campaign, product, event, or content data. Pixelixe turns those records into branded image outputs by mapping fields such as title, image URL, price, CTA, status, category, and locale into a reusable template.
Use Airtable for record management, approval status, campaign fields, product data, and content operations.
Use Pixelixe for template rendering, brand consistency, output generation, and image URL handoff.
Use automations, Make.com, Zapier, n8n, or a backend when records should generate images automatically.
Airtable fields to Pixelixe template layers
The most reliable workflow starts with stable field names in Airtable and stable layer names in Pixelixe.
| Airtable field | Pixelixe layer | Generated output use |
|---|
| Title or headline | headline text layer | Social cards, product promos, launch graphics, and event banners. |
|---|
| Attachment or image URL | image layer | Product photos, cover images, speaker photos, screenshots, or campaign visuals. |
|---|
| Price, offer, badge, or category | badge and label layers | Ecommerce promos, localized offers, feature tags, or content categories. |
|---|
| Status or approval field | workflow routing | Generate only approved records or route draft outputs for review. |
|---|
| Locale or market | copy and template variant | Localized campaign images and market-specific visual variants. |
|---|
Airtable record to Pixelixe payload
Use this payload shape from a backend, automation tool, or Airtable-connected workflow.
API request
POST https://studio.pixelixe.com/api/graphic/automation/v2
Content-Type: application/json
{
"document_uid": "airtable_visual_template_uid",
"api_key": "YOUR_API_KEY",
"format": "json",
"image_type": "png",
"modifications": [
{ "element_name": "headline", "type": "text", "text": "{{fields.Title}}" },
{ "element_name": "image", "type": "image", "image_url": "{{fields.ImageUrl}}" },
{ "element_name": "badge", "type": "text", "text": "{{fields.Category}}" },
{ "element_name": "cta", "type": "text", "text": "{{fields.CTA}}" }
]
}
Generated output
{
"status": "success",
"image_url": "https://studio.pixelixe.com/storage/file/.../airtable-generated-image.png",
"source_record_id": "recXXXXXXXXXXXXXX"
}
Write the returned image_url back to an Airtable URL field when the generated asset should remain attached to the record.
Airtable image workflows worth automating
These record-driven workflows have strong business intent because teams already manage the data in Airtable.
Content calendar visuals
Generate social cards, blog images, or newsletter graphics from approved content calendar records.
Product and promo cards
Render product images, prices, discounts, collection labels, and campaign CTAs from commerce records.
Event and webinar graphics
Create speaker cards, session banners, date graphics, and sponsor visuals from event tables.
Approval-ready creative operations
Generate draft images from records and route the result through Airtable status fields or review steps.
Airtable implementation workflow
Use Airtable for structured records, then trigger Pixelixe only when the record is ready.
Create the table
Define fields for title, source image, CTA, offer, category, locale, approval status, and output URL.
Create the template
Name Pixelixe layers to match Airtable fields so mappings are easy to maintain.
Trigger rendering
Call Pixelixe from Make.com, Zapier, n8n, Airtable automation, or a backend when a record is approved.
Store the output
Write the generated image URL back to Airtable and route it to CMS, email, social, or storage.
Related Pixelixe workflows
Use these connected pages to evaluate the implementation path, adjacent use cases, and Pixelixe product fit.
