All integrations Available now
Digital Asset Management
Widen Collective (Acquia) + Ignite Lean
Widen (Acquia) DAM runs at many large brands. Bridge approved media to production.
REST API Webhooks
How the Connection Works
Widen Collective (Acquia)
REST APIWebhooks
Ignite Lean
Into Ignite Lean
- Approved media + metadata
Back to Widen Collective (Acquia)
- As-built media
How It Works
- 1Widen publishes via REST.
- 2Ignite Lean embeds in work instructions.
- 3As-built media uploads back.
Recommended Workflows
How Widen Collective (Acquia) works best with Ignite Lean. These are recommended patterns: Ignite Lean fires the trigger, and how Widen Collective (Acquia) routes it (which work group, which device, which rule) is configured to your IT setup.
Approved photos drive the kiosk
Trigger A new approved photo is published in Widen Collective (Acquia)
- 1Widen Collective (Acquia) fires the asset-approved event.
- 2Ignite Lean swaps the photo in the matching work instruction step.
- 3Operators always see the current approved visual.
No mismatched visuals on the floor, no manual sync.
As-built photos upload back with metadata
Trigger An operator captures an as-built photo
- 1Ignite Lean attaches the photo to the build with serial, operator, and timestamp.
- 2The connector uploads the photo to Widen Collective (Acquia) with that metadata.
- 3Marketing + quality find evidence by serial in their normal tool.
Audit + warranty evidence lives in the brand DAM organized for retrieval.
Connect Widen Collective (Acquia) today
This works now through our REST API, outbound webhooks, and Excel/CSV. Start with the API reference, or talk to us about a guided setup.