Skip to content
DOTWICK
Start free

Make

What it does

A Watch module starts a scenario the moment something happens in Dotwick. The other modules create or change things in your workspace, or look them up. The Watch modules are instant: Make registers a webhook with Dotwick when you turn the scenario on and removes it when you turn it off.

It needs an API key, so your plan must include API access and webhooks (see the pricing page). The app uses the same scopes, role limits, folder restriction and rate limits as any other key.

Connect your workspace

In Dotwick, open Settings → API and create a key with the For Zapier / Make preset. It asks for these scopes: codes:read, codes:write, analytics:read, submissions:read, folders:read, folders:write, tags:read, tags:write, webhooks:read, webhooks:write. In Make, add a Dotwick connection and paste the key. Make tests it with GET /v1/workspaces/current.

Watch modules need a key made by an admin or the owner, because each one registers a webhook.

Watch modules

The first five can follow one code, one folder (with its subfolders) or one tag. To follow one scan alert rule, add a filter on the rule id in the scenario.

  • Watch Scans: a person scans a code. Bots and link previews never trigger.
  • Watch New Codes: a code is created in the app or through the API.
  • Watch Code Updates: a code's destination, content, name, design or rules change.
  • Watch Form Submissions: someone answers a form code or a form block.
  • Watch Scan Alerts: a scan alert fires: every scan, N scans in M minutes or no scans for D days.
  • Watch Bulk Runs: a bulk run ends, with its counts.

Actions and searches

  • Create a Code, Update a Destination, Pause or Resume a Code and Add or Remove Tags.
  • Create a Folder.
  • Create a Report: render a PDF or CSV analytics report and get its link.
  • Search Codes, Search Tags, Search Folders and List Scan Alerts.
  • Get Code Scans: the scan totals of one code for a range.

How the webhooks are handled

Each Watch module registers one hook with POST /v1/hooks and removes it with DELETE /v1/hooks/{id}. A hook is a webhook with one event, signed and retried like any other. A workspace can have up to 100 hooks, and the Developers screen lists them apart from your own endpoints.

The Scan Alert module receives an alert.fired event. See Event types for its fields.