Check a Cincopa upload without opening another tab
When someone needs an update on a media import, a webhook request can ask Notis to check the Cincopa status ID and send back a report.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Asset Upload From URL Status
Tool to check the status of an asset upload initiated via url by its status id. use after calling 'upload asset from url' to poll for completion.
Why this helps
People lose time reopening Cincopa to check uploads and relaying status updates by hand.
- Check an upload using its Cincopa status ID when an update is needed.
- Send the status report to a channel the team already checks.
- Avoid repeated manual visits to the upload screen.
Setup
Build it in a few focused steps.
- 1Connect Cincopa once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, ask Notis to check the Cincopa upload status for the status ID provided with the webhook request and report the result.
- 4Pick a webhook trigger and choose where run reports go.
- 5Test by sending one real Cincopa upload status ID to the webhook.
Questions about this workflow
What information should the webhook request include?
Include the status ID returned when the Cincopa URL upload was started.
Does this start or retry an upload?
No. It checks the status of an upload that was already started.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Cincopa. A trigger fires from one place; an action lands in another.
Jira triggers
Cincopa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Upload Asset From URL
Tool to upload a new asset directly from a provided external url and receive a status id for tracking. use when you need to import media from a remote source and optionally specify a gallery or existing asset.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Abort Asset Upload From URL
Tool to abort an ongoing asset upload-in-progress by providing its status id. use when an upload is no longer needed, was initiated by mistake, or is taking too long.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get Asset Upload From URL Status
Tool to check the status of an asset upload initiated via url by its status id. use after calling 'upload asset from url' to poll for completion.
New Project
Triggered when a new project is added in Jira
Validate API Connection
Tool to validate api connection. use after obtaining a valid api token to confirm connectivity.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira and Cincopa, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cincopa.