Iconik integration

What it does

The Iconik integration lets your agency drive a client's Iconik media library from inside any workflow. Connect once with the client's App-ID and Auth-Token, and your workflows can search the asset catalog for footage that matches a brief, fetch the metadata for a specific clip when a downstream system needs a reference, and create new collections to group deliverables for review and handoff. The integration is action-only, so an Iconik action runs whenever another trigger (a form submission, a schedule, an upstream webhook) fires inside the workflow.

Connect an Iconik account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Iconik and click Connect.
3. In a new tab, sign in to the client's Iconik account and open Admin, then App Tokens.
4. Create an App Token scoped to the smallest set of permissions the workflow needs, and copy both the App-ID and the Auth-Token.
5. Paste the App-ID and Auth-Token into TaskJuice and save the connection.

To rotate or revoke access later, return to the Iconik Admin App Tokens panel, delete the entry, create a new token, and update the TaskJuice connection.

Triggers

Iconik does not publish a public webhook surface that fits the standard envelope, so the integration is action-only. Drive Iconik actions with a Schedule trigger, a polling trigger from another app, or an inbound webhook from a different source.

Actions

• iconik/search-assets runs a free-text search against the client's asset library, with optional filtering by document type, and returns one page (up to 100 results) of matches.
• iconik/get-asset fetches the full metadata for a single asset by its Iconik asset ID, including title, status, type, and timestamps.
• iconik/create-collection creates a new collection with a title, optional description, and optional parent collection so workflows can group assets for review, share-outs, or client handoff.

Known limitations

• The integration calls the Iconik REST API with the connected App-ID and Auth-Token. Per-token rate limits, storage quotas, and feature entitlements are governed by the client's Iconik plan, not by TaskJuice. When Iconik returns a 429, TaskJuice surfaces it as a retryable rate-limit error.
• The integration ships the three highest-leverage actions for agency workflows (search, get, create collection). Direct asset upload, transcoding, and per-asset ACL changes are not first-class actions yet. Use a follow-up HTTP step against the Iconik API if your workflow needs a verb that is not listed above.
• The integration is action-only. To react to Iconik events in real time, schedule a poll of search-assets with a date filter, or trigger workflows from the source system that is uploading to Iconik (form, file-watcher, upstream webhook).