Automation integrations
Make
Add invisible watermarking and watermark detection to a Make scenario. Connect your Etchv account, then add modules to submit jobs and collect results.
Add watermarking or detection to a Make scenario. Request early access to have the app shared with your organization.
Connect your account
Create an API key with watermarks:embed, watermarks:detect and/or assets:read, then save it in Make. Connection testing uses no credits.
Assemble a scenario
| Step | Configuration |
|---|---|
| Submit Watermark / Submit Detection | Map the filename and binary file data. Choose Image, PDF or Video |
| Reference and retry key | For embedding, supply non-empty JSON. Map an idempotency key (a value you choose so a retry isn't run twice) based on the source event, so it stays the same |
| Get Job Status | Check status_url about once a minute while the job is pending, up to 35 minutes |
| Get Watermarked File | When embedding succeeds, collect the binary output using result_url |
| Get Detection Result | When detection succeeds, collect the JSON using result_url |
| Handle failure | Send request_id and error_code to your error handler |
- Submit Watermark / Submit Detection
- Configuration
- Map the filename and binary file data. Choose Image, PDF or Video
- Reference and retry key
- Configuration
- For embedding, supply non-empty JSON. Map an idempotency key (a value you choose so a retry isn't run twice) based on the source event, so it stays the same
- Get Job Status
- Configuration
- Check
status_urlabout once a minute while the job is pending, up to 35 minutes
- Get Watermarked File
- Configuration
- When embedding succeeds, collect the binary output using
result_url
- Get Detection Result
- Configuration
- When detection succeeds, collect the JSON using
result_url
- Handle failure
- Configuration
- Send
request_idanderror_codeto your error handler
Give file-result modules a filename with the original extension. Download Asset gets a kept file by its asset_id.
To retry, send the same inputs with the same idempotency key. Collect job results within 24 hours. If you chose a bucket, check storage delivery separately. A successful watermark does not mean the file reached your bucket.
Many files at once
Create Batch watermarks up to 100 files in one call. Put the files in one zip of up to 55 MB (Make's Archive module can create it), map it, and list every file in Items with its exact path in the zip and its own reference data:
[{"filename": "contracts/acme.pdf", "data": {"recipient": "acme"}},
{"filename": "contracts/globex.pdf", "data": {"recipient": "globex"}}]The batch starts at once. Check it with Get Batch about once a minute until status is completed, failed or cancelled, then collect each file with Get Watermarked File and the item's result_url.
With Zip the results on, Download Batch Zip gets every result as one zip once archive_status is ready, with a manifest.json listing the files and any failures. Each file costs the same credits as a single request, and files that fail are refunded; error_code on each item says why. Reuse the same idempotency key on retry to get the same batch back.
Make modules send each request as one body, so Create Batch takes the files as a zip rather than uploading them one by one.
See shared workflow requirements and async jobs.
Traceable links
Create Traceable Link shares a file from your asset library so each recipient opens their own watermarked copy. Map the original's asset_id (a source asset, such as source_asset_id from a watermark job), a name, and either recipients' email addresses or allowed domains, with an idempotency key. Add each address to Recipients, or each domain to Allowed domains.
The step returns the link with its url; send it to your recipients in your own email or chat step, because Etchv does not send it. Each copy costs one embed of the file, charged when it is made. The key needs links:write. See traceable links.