Skip to content
DOTWICK
Start free

Zapier

What it does

A trigger starts a Zap when something happens in Dotwick. An action changes something in your workspace. A search looks something up and hands it to the next step. Triggers are webhooks that the app sets up and removes for you, so you never register an endpoint by hand.

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. Then, in Zapier, add the Dotwick connection and paste the key. Zapier tests it with GET /v1/workspaces/current.

Triggers need a key made by an admin or the owner, because each one registers a webhook. Actions and searches work with the scopes above.

Triggers

New Scan, New Code, Code Updated, New Form Submission and Scan Alert can follow one code, one folder (with its subfolders) or one tag. Dotwick applies the filter before it records a delivery, so a Zap that watches one folder is not woken by the rest.

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

Actions and searches

  • Create Code: a dynamic URL code with a name, a destination, a folder and tags.
  • Update Destination: point a code at a new address.
  • Pause or Resume Code.
  • Add or Remove Tags on one or more codes.
  • Create Folder.
  • Create Report: render a PDF or CSV analytics report and get its link.
  • Find Code, Find Tag, Find Folder and Find Scan Alert.
  • Get Code Scans: the scan totals of one code for a range.

N scans in M minutes

Make a scan alert rule in the app (for example 50 scans in 10 minutes on a folder), then use the Scan Alert trigger. Every time the rule fires, the trigger gets an alert.fired event with the rule, the scope, the number of scans and the window. See Event types for its fields.

What the app registers

When a Zap with a trigger is turned on, the app calls POST /v1/hooks. It deletes the hook with DELETE /v1/hooks/{id} when the Zap is turned off. Each hook is a webhook with one event, signed and retried like any other, and the workspace can have up to 100. GET /v1/hooks/samples/{event} returns up to 3 recent events so you can map fields while you build.

POST /v1/hooks
{  "event": "scan.created",  "targetUrl": "https://hooks.example.com/catch/12345/abcdef/",  "app": "zapier",  "filter": {    "folderId": "fld_7c2d9e41a05b3f68"  }}

Ready-made Zaps

Google Sheets, HubSpot and Slack go through Zapier. There is no separate Dotwick add-on for them; if you need a native one, tell us.

  • Add new Dotwick scans to Google Sheets rows
  • Save Dotwick form answers to Google Sheets
  • Log new Dotwick codes in Google Sheets
  • Create HubSpot contacts from Dotwick form answers
  • Post Dotwick scan alerts to a Slack channel