Home | Connectors | Slack | Slack - Centric Integration and Automation
Direction: Centric to Slack
When a product record reaches key lifecycle stages in Centric, such as concept approval, sample sign-off, costing approval, or launch readiness, Slack can notify the relevant channel automatically. Product managers, design teams, sourcing, and marketing stay aligned without manually checking Centric for status updates.
Business value: Improves visibility into product development progress, reduces missed handoffs, and speeds up decision-making across teams.
Direction: Centric to Slack
Centric can send alerts to Slack when an approval is overdue, a task is blocked, or a required review has not been completed within a defined SLA. Notifications can be routed to a project channel or directly to responsible stakeholders so issues are addressed quickly.
Business value: Reduces launch delays, improves accountability, and helps teams resolve bottlenecks before they affect timelines.
Direction: Slack to Centric
Teams can submit new product ideas, design requests, or change requests from Slack using a structured form or workflow that creates a record in Centric. This is useful for merchandising, sales, or regional teams that often capture requests in chat but need them formalized in the PLM process.
Business value: Prevents requirements from being lost in conversation, standardizes intake, and creates a traceable path from request to execution.
Direction: Bi-directional
When a product specification, BOM, or design file is updated in Centric, Slack can notify the review group. Team members can discuss the change in Slack, then trigger an approval or comment update back in Centric once consensus is reached. This supports fast-moving design and merchandising workflows where multiple functions must review changes quickly.
Business value: Shortens review cycles, keeps discussion tied to the right product record, and improves collaboration across design, sourcing, and quality teams.
Direction: Centric to Slack
Centric can post updates to Slack when sample status changes, such as sample received, sample under review, revisions requested, or sample approved. Teams can use the Slack channel to coordinate feedback from design, product development, and quality assurance while Centric remains the system of record for sample status.
Business value: Speeds up sample iteration, reduces email back-and-forth, and improves transparency during development cycles.
Direction: Centric to Slack
Centric can notify Slack when required product attributes, images, or compliance fields are missing before a product can move to the next stage. The alert can include the missing items and the owner responsible for completion.
Business value: Improves data completeness, reduces downstream rework, and supports cleaner handoff to PIM, DAM, and commerce systems.
Direction: Centric to Slack
As a product approaches launch, Centric can trigger Slack updates to marketing, sales, operations, and customer support channels with launch dates, approved assets, and final product details. This gives downstream teams early visibility into what is ready and what still needs attention.
Business value: Aligns go-to-market execution, reduces launch-day surprises, and ensures teams work from approved product information.
Direction: Bi-directional
If a product issue is raised in Slack, such as a supplier delay, spec conflict, or compliance concern, the conversation can be linked to or create an issue in Centric. Updates from Centric can then be posted back to Slack as the issue moves through resolution.
Business value: Creates a clear audit trail, improves issue ownership, and helps teams resolve product risks faster with less manual follow-up.
CyanGate, LLC
+1 (833) DAM-XPRT (326-9778) 
contactus@oneteg.com
