Save new Pimcore records to an Airtable base for the catalog team
When Pimcore fires its postAdd event for a newly added element, this workflow creates an Airtable record from it, so your catalog team can review new entries in a base without working inside Pimcore.
Pimcore
Airtable2 steps Setup ~5 min Used on 1.7k sites Free to import
What this workflow does
Pimcore holds your product and content data, but not everyone on a catalog team works in it every day. Merchandisers, copywriters and photographers often prefer a simple table where they can see what is new and note what still needs doing. This workflow copies each new Pimcore element into an Airtable base for them.
The Pimcore trigger listens for Pimcore's postAdd event, which happens after a new element has been added and saved. The data sent with that event is passed to the Airtable step, which creates a record in the base and table you choose. You map the Pimcore values you care about, such as the element's key, path or product fields, into your Airtable fields.
The template only reacts to additions. Edits to existing elements do not change the Airtable record, and each new element becomes one new record. Run a test after import to see exactly which values Pimcore sends with the event, and which kinds of element reach the workflow in your setup.
Enrichment queue for new products
Each new product added in Pimcore appears in Airtable, where copywriters add a status column and work through descriptions that still need writing.
Photo shoot planning
The studio team watches the Airtable base for newly added products and plans which items need photographing next.
Weekly catalog review
A category manager filters the base by the date records were created to review everything added to Pimcore that week.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Pimcore Post AddRuns on Pimcore's postAdd event, after a new element is added. The data sent with that event becomes available for mapping into the Airtable record.
- Airtable Create Record
Creates an Airtable record for the new Pimcore element in the base and table you choose. Map the Pimcore values into your fields and add a test element to check the record.
What you need
- FlowMatticCore
- Pimcore AccountAccount
- Airtable AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Add a Filter after the Pimcore trigger that continues only for elements under one path or of one class, if only products should reach the catalog base.
- Add a status field in Airtable with a default value such as To review, so the catalog team can track each new record without extra mapping.
- Add one test element in Pimcore after import so FlowMattic captures real event data, then map the fields before turning the workflow on.
Questions about this workflow
Does editing a Pimcore element update its Airtable record?
No. The workflow only runs on postAdd, when an element is added. Pimcore's Post Update trigger exists if you want to handle edits in a separate workflow.
Which Pimcore elements reach Airtable?
Whatever your Pimcore setup sends for the postAdd event. Add a test element of each kind you use and check the captured data to see what arrives.
Are Pimcore elements added before import copied to Airtable?
No. Only elements added after the workflow is switched on create Airtable records.
More Data Sync workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted