Pimcore holds product data, assets and master records. FlowMattic posts the events around them to Slack: an updated product to merchandising, a failed save to the developers, a deleted object to an audit channel and a finished CSV export to whoever asked for it. For PIM, ecommerce and data teams who run Pimcore.
12 triggers14 actions6 example workflows2 ready-made templatesUnlimited runs
Try a pairing
When this happens in Pimcore12 triggers
Do this in Slack14 actions
1. TriggerPost Update
2. ActionSend Channel Message
When Pimcore fires Post Update, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Pimcore and Slack workflows you can build
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made template
Post a Slack alert when a Pimcore object is updated
Each saved change posts the object, class and user to the product data channel, so merchandisers see edits to products they look after without opening Pimcore.
Post Update Failure fires when a save does not complete. The developers get the object and error in a private channel, so a broken import or validation rule is fixed quickly.
Post Update Failure→Send Private Channel Message
Keep an audit trail of deleted objects
Post Delete posts what was removed and by whom to a private audit channel, so a product that disappears from the shop can be traced back.
Post Delete→Send Private Channel Message
Tell merchandising about new products only
Post Add fires for every new object. A Filter passes only the product class, so the merchandising channel is not filled with folders and assets.
Post Add→Filter→Send Channel Message
Announce finished CSV exports
Post CSV Item Export posts to the channel of the team waiting for the export, so they know the file is ready for a marketplace feed or a supplier.
Post CSV Item Export→Send Channel Message
Route updates to each category owner
A Router reads the object path or class, so changes under apparel reach the apparel team and changes under electronics reach theirs, each in their own channel.
Send Channel MessagePost or Schedule a new message to a specific #channel
Add ReminderAdds a reminder for the user
Create ChannelCreates a new channel
List All ChannelsRetrieve list of all channels
Set Channel TopicSets the topic on a selected channel
Set StatusSets your Slack status to the given text and emoji
Invite User To ChannelInvite an existing User to an existing Channel. You must be a member of the channel to invite someone to it
Find User by EmailFinds a user by matching against their email instead of their username
Find User by IDFinds a user by their ID.
Send Direct MessageSend a direct message to a user or yourself from the Slackbot. Can also schedule a message for later
Send Private Channel MessagePost a new message to a private channel you choose. Can also schedule a message for later
Update ProfileUpdate basic profile fields such as name or title
Find MessageFinds a Slack message using the Slack Search feature
Upload FileUpload file to your slack workplace
Why run this pair with FlowMattic
Pimcore and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Data changes are visible
Edits, failures and deletions reach the people who own each part of the catalogue, so mistakes are caught before they reach the shop.
Product data stays with you
Events pass through your own WordPress server on the way to Slack, not through another company's automation account.
Big imports, same cost
Runs are unlimited on every FlowMattic plan, so a catalogue update that touches thousands of objects costs nothing extra.
Common questions
How do I send Pimcore events to Slack?
Create a FlowMattic workflow with a Pimcore trigger such as Post Update, follow its setup instructions, then add Slack Send Channel Message with the object, class and user mapped into the text.
Can I hear only about failed saves?
Yes. Post Add Failure, Post Update Failure and Post Delete Failure are separate triggers. Build workflows from the ones you need and post them to a developers' channel.
Will a bulk import flood Slack?
It can, because each saved object fires the trigger. Add a Filter on class or path, or post imports to a quiet channel.
Can copies of objects be posted too?
Yes. Post Copy fires when an object is copied. It is useful when teams duplicate products as a starting point for new ones.
Can I log changes as well?
Yes. Add a Google Sheets or WP Tables step to the same workflow, so each change is posted to Slack and kept as a searchable log.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Pimcore integration 1.0.0, Slack integration 1.0.