Why connect Aprimo
Gradial produces real files. A generated hero image, a smart-cropped variant, a campaign brief, a copy doc, a QA report — all of it comes out of the work as an artifact. Without a DAM connection, getting those files into Aprimo is a download, a re-upload, and a metadata form filled in by hand, which is exactly the manual step the rest of the workflow removed. Connecting Aprimo closes that gap. Grady uploads what it creates straight into your DAM, in the classification you specify, and confirms the record landed.This integration is an upload destination. Grady files assets into Aprimo and verifies the resulting records — it does not read your existing Aprimo library or search it. For search and retrieval across your asset estate, see Asset Search.
What Grady can do
Records are always created with a draft status, so nothing Grady files enters an approved state without a person reviewing it.
Prerequisites
- An Aprimo tenant and the subdomain used to reach it (the part before
.aprimo.com) - A registered client in Aprimo with a client ID and client secret
- The classification ID of the destination you want Grady to file into
- An Aprimo administrator to grant the client permission to create records in that classification
Set up the connection
1
Register a client in Aprimo
In Aprimo, create an API client for Gradial and record its client ID and client secret. Grant it permission to create records in the classification you intend to use as the destination.
2
Find your classification ID
Open the destination classification in Aprimo and copy its ID. Gradial accepts either the 32-character form or the hyphenated UUID form.
3
Add the integration in Gradial
Go to Settings → Integrations, find Aprimo under Design & assets, and select Connect. Provide:
4
Validate
Save the connection. Gradial validates the credentials against your tenant and reports the result immediately. If validation fails, the message names the field at fault.