Notion sync
Link a template to one of your Notion databases and every submission becomes a row there — created when the form is submitted, updated when the document changes afterwards.
1 · Connect your workspace
In Notion, create an internal integration at notion.so/my-integrations (Pocper's Settings links to it) and copy its internal integration secret. Paste it in Pocper under Settings → Integrations → Notion. Only the team owner can do this; the secret is stored encrypted. To change it, use Replace token on the same page — the new secret is checked before it replaces the old one.
Then share the database you want to write into, or the page it sits in, with the integration: in Notion, open it, choose ••• → Connections → Add connections (some versions put Connections under ••• → More) and pick your integration. Without this, the database is missing from Pocper's list and a pasted link to it is reported as not found.
2 · Link a template to a database
Open the template's Workspace panel, choose the Integration tab and press Link a Notion database. Pick a database your integration can see (type to search) or paste its link. The first row, New database, creates one in a page you choose, with a column for every field, already mapped, plus a Pocper ID column.
Each field gets a picker of the columns its type fits: a date to a date column, a checkbox to a checkbox, text to text or the title. Under Submission details you can also map the client, when it was submitted, its status and who submitted it.
Each document made from the template copies these settings when it is created, and its own Integration tab can change them for that document alone. A later change on the template reaches only new documents; for older ones that still follow it, the template offers Apply to them too. A document made before the template was linked offers Use the template's settings.
3 · What happens on submit
When a form is submitted — by the person filling it in, or by you marking it submitted — a row is created within seconds. Under Sync, the document's Integration tab then says when it last synced, with a link to the row, or that a change is waiting or failed; Sync now appears only if sending failed or the document was never sent. To create the row as soon as the document exists instead, change When to sync in the template's Integration settings.
Later edits update the same row a few seconds after the last change, and cancelling a document updates its status column.
The row's page gets a bookmark back to the document and the answers as a list (long answers shortened, at most a hundred). The template's Integration settings can turn the page body off.
4 · Files, signatures and duplicates
Uploaded files and signatures can go to a Files & media column: the file is copied into Notion, up to 20 MB (a larger one is skipped and noted on the sync log). Sending them as links to a URL column is a separate switch, off by default, because anyone who can see the row could open such a link without signing in to Pocper.
The duplicate guard keeps a retried submission from appearing twice: Pocper writes each document's Pocper ID into a text column of that name and finds the row by it. A database that already has that column uses it; otherwise the link dialog adds it (the box is ticked by default), or the Integration tab's Settings add it in one click.
5 · Changes made in Notion
Turn on reverse sync in the Integration tab and two things come back from Notion. Setting the status column to Submitted, Cancelled or Collected moves the document to that status; editing a cell mapped to a text, checkbox, date or time field writes it into the document, and its history shows the edit as coming from Notion. If both sides changed a cell, Notion's value wins — unless a client is still filling the form in (not submitted, and saved in the last ten minutes): then their value stays, Notion's cell is put back, and the Integration tab notes it.
Reverse sync needs a webhook, set up once per team by the owner under Settings → Integrations → Notion: create the webhook URL, add it as a subscription in your integration's Webhooks tab in Notion, and paste back the verification token Notion sends. Pocper never polls Notion, so without it, edits in Notion stay there. A column that cannot take a value back — a signature, a file, any field of a locked document — is changed back in Notion, and the Integration tab notes it.
6 · When something goes wrong
A row that could not be sent is retried, with growing gaps, for a day. If that runs out, or Notion refuses outright — the secret was revoked, or the database is no longer shared — syncing stops, and the team owner and whoever linked the database get an in-app notification that opens the document's Integration tab. The error there says what to do; Notion's own message is under Show Notion's message.
A stopped sync resumes by itself once the cause is fixed: after you reconnect or replace the token in Settings, after Pocper reads the database again (Reload properties from Notion on the Fields heading, or any change saved on the Integration tab), or when the document is edited. On the template, the Sync log row counts the failures and can show just those, and a line such as “3 documents aren't in Notion yet” has a Send button that sends them all — adding the Pocper ID column first if it is missing; unfold it to see which and why. Pause syncing, beside the Sync heading, stops sending changes until you press Resume syncing.