Send a webhook to an external system after a Pimcore CSV export

When Pimcore raises its postCsvItemExport event during a CSV export, FlowMattic posts the event data as JSON to a webhook URL you choose, so an external system learns what was exported.

Pimcore

Webhook Outgoing

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 571 sites Free to import

The Send a webhook to an external system after a Pimcore CSV export workflow on the FlowMattic canvas, with 2 steps across Pimcore, Webhook Outgoing — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Teams export product and master data from Pimcore as CSV for shops, marketplaces and partners. The system that consumes that data often needs to know when an export happened and what was in it. This workflow passes Pimcore's export event to that system through a webhook.

The Pimcore Post CSV Item Export trigger listens for Pimcore's postCsvItemExport event. As the name says, the event is about items in a CSV export, so a single export of many objects can start one run per exported item rather than one run for the whole file. FlowMattic receives the data Pimcore sends with each event.

The Webhook Outgoing Submit Data to Webhook step then sends that data with a JSON POST request to the URL you enter. The step ships with no URL and no mapped data, so after import you add the receiving address and map the Pimcore values the external system expects, such as the object's ID or key.

Before pointing this at a production system, run a small export of two or three objects. Task History shows how many runs started, what Pimcore sent each time and what the receiving URL answered, which tells you whether the receiver should expect one call per item.

Notifying a marketplace connector

A retailer's middleware gets a webhook for each product in a Pimcore CSV export, so it can queue those products for the next marketplace upload.

Export audit trail

A data team posts export events to an internal logging endpoint, recording which Pimcore objects went out in each CSV and when.

Partner feed refresh

A manufacturer pings a distributor's API when items are exported, so the distributor knows fresh product data is on its way.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Pimcore Post CSV Item Export
Starts a run when Pimcore raises its postCsvItemExport event during a CSV export. The data Pimcore sends with that event is passed to the webhook step; a large export can start many runs.
Step 2Action
Webhook Outgoing Submit Data to Webhook
Posts the Pimcore event data in JSON format to the external webhook URL. The template leaves both the URL and the data empty, so add the address and map the values the receiver needs.

What you need

FlowMatticCore
Pimcore 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.

If the receiver should get one notice per export rather than per item, have it group incoming calls by a value they share, such as a timestamp, since each exported item can arrive as its own request.
Send only the identifiers the external system needs, such as the object ID, rather than every field, to keep each request small when exports are large.
To send only certain object types, put a Filter between the Pimcore trigger and the webhook step on a class or type value, if a test run shows one.

Questions about this workflow

Does a Pimcore CSV export send one webhook or one per item?

The trigger listens for postCsvItemExport, an item-level event, so expect it to fire for exported items rather than once per file. Run a small export and count the runs in Task History to see how your setup behaves.

What data does the external system receive from Pimcore?

Only the values you map in Submit Data to Webhook, sent as JSON with a POST request. Check a test run to see which fields Pimcore includes with the event.

Does the webhook include the CSV file itself?

No. The step posts the event data you map, not the exported file. If the receiver needs the file, share it from where Pimcore saves your export.

Can I send the Pimcore export data to an API that isn't a webhook?

Yes. Swap Submit Data to Webhook for API by FlowMattic, which can send other request methods and custom headers to the API you use.