Signed contracts in a Notion database

Set up the database

Create a database, called a data source in Notion's newer terms, with a property for each thing you want to see: a title for the client or contract name, an email property, number properties for prices, a date property for Signed on, and a text property for the envelope ID. Then make sure the automation tool's Notion connection has access to it, or the tool won't find it.

Connect it

1. 1

   Catch the webhook

   Create a Zapier Catch Hook, a Make Custom webhook or an n8n Webhook node, then add its URL in Settings › Developers › Webhooks with envelope.completed ticked.

2. 2

   Sign a test contract

   Sign one made from your template, so real labels and values reach the tool.

3. 3

   Add the Notion step

   Use Create Data Source Item in Zapier, Create a Data Source Item in Make, or the Notion node's Database Page Create operation in n8n, and choose your database.

4. 4

   Map the properties

   Title from data.envelope.title, Envelope ID from data.envelope.id, Signed on from data.envelope.completed_at, and the answers from data.fields_by_label.

5. 5

   Turn it on

   Publish the Zap, scenario or workflow. Each completed contract now becomes a page.

Make the most of it

• Add a Status property and a board view, so signed jobs move from Signed to Scheduled to Done as your team works them.
• Relate each page to a Clients database, so every contract for a client collects in one place.
• Notion number properties need plain numbers. If a price arrives with a currency symbol or commas, strip them with a formatter step first.
• Save the PDF somewhere lasting. The link in data.signed_pdf.url expires after 24 hours, so upload the file to your storage and put that link on the page.

Why not a direct connection?

Notion's own automations can send webhooks out, but a database can't receive one from another app, which is why a tool sits in the middle. If you'd rather not add one, a template's Responses tab exports every answer to CSV, and Notion can import a CSV as a database.