How a Small Nonprofit Connected Fundraising Forms to Salesforce with Zapier
A small nonprofit connected fundraiser, school, and sponsor sign-up forms to Salesforce with Zapier, merged duplicate workflows, and added error alerts.
How to Build a Notion CRM for Cognito Quotes
Build a practical Cognito to Notion CRM integration with Zapier, CSV migration, Gmail filtering, and views that keep quotes, owners, and follow-ups organized.
TABLE OF CONTENTS
Cognito to Notion CRM integration works best as a split architecture: keep Cognito Forms for complex quote capture, use Zapier to send new submissions to a Notion database, and make Notion the working CRM for statuses, assignments, pipeline views, relationships, and follow-up. Import historical quotes once, then use selective Gmail automation so only relevant conversations enter the CRM.
The split architecture for a Cognito to Notion CRM integration
Each tool should handle the job it does best:
- Cognito Forms: capture detailed quote requests with conditional logic, paginated questions, and calculations.
- Zapier: move new submissions between Cognito Forms and Notion without manual re-entry.
- Notion: manage quote status, ownership, customer context, pipeline views, and follow-up work.
- Gmail: remain the communication layer, with only important threads sent into the CRM.
This gives the team a single working view without forcing a complex quote form into a database that wasn't built to replace it. For the automation layer, Zapier can create or update records in Notion as new quote events arrive.
Step 1: Design the quote CRM before connecting anything
Start with one Quotes database and define the fields the team needs to act on a quote. Keep the first version focused. A useful starting set includes:
- Quote or submission ID
- Customer name and email
- Quote date
- Service or product requested
- Estimated value
- Pipeline stage
- Assigned owner
- Next follow-up date
- Last contact date
- Source, such as Cognito, email, phone, or manual entry
- Notes and customer context
Use a select property for the pipeline stage, such as New, Reviewing, Quoted, Follow-up, Won, and Lost. Use an owner property so each teammate can create a personal view without maintaining a separate database.
Add relationships when one customer can have multiple quotes
If repeat customers may submit more than one quote, create a separate Contacts database and relate each quote to a contact. Rollups can show open quote count, latest stage, or total quoted value from the contact record. This prevents duplicate customer records and gives the team a history of every quote tied to the same person.
Step 2: Connect new Cognito submissions with Zapier
Build the automation around a new Cognito entry. Cognito's Zapier integration is available on its Pro, Team, and Enterprise plans (as of October 2026, check current plans). The basic workflow is:
- Use the Cognito Forms New Entry trigger, which fires when a quote is submitted.
- Find an existing contact or quote using a stable identifier, such as the Cognito entry ID or customer email.
- Create a new Notion quote record, or update the matching record if the workflow is designed for edits.
- Map the form fields into the quote database.
- Set an initial stage and assign an owner when the routing rules are known.
- Log an error or send an alert when required fields are missing.
We use the Cognito entry ID as the external ID whenever possible. It gives the automation a reliable way to recognize the same submission and reduces duplicate quote records.
Don't try to recreate every calculation and conditional question inside Notion. Let Cognito produce the completed quote data, then send the fields the team needs for review and follow-up.
Step 3: Import historical quotes once
A live Zapier connection handles new submissions after setup. It doesn't backfill the old entries. Export the historical Cognito entries to Excel from the form's Entries page, save the cleaned sheet as a CSV, and import that file into Notion.
Before importing, normalize:
- Names and email addresses
- Date formats
- Stage values
- Owner names
- Currency and number fields
- Duplicate customer records
- Empty values and placeholder text
Keep the original Cognito entry ID in the imported records. After the import, test a few old records against Cognito so the team can trust the new CRM view. Historical data can then be treated as a starting point, while the Zap handles the ongoing flow.
Step 4: Build views around the work, not the database
A single table is useful for setup, but the team will work faster with views that answer specific questions. Start with:
All quotes
Show every record with stage, owner, value, last contact, and next follow-up date. This is the administrative view for cleanup and reporting.
My quotes
Filter the owner property to the current user. Each teammate sees the records assigned to them without maintaining separate filtered databases.
Pipeline board
Group a board view by stage. This makes it easy to see which quotes are new, in progress, awaiting follow-up, won, or lost.
Follow-ups due this week
Filter by next follow-up date and exclude closed stages. This creates a short action list instead of making the team scan the full quote table.
Long time no contact
Add a formula for days since last contact and filter for records above the threshold that matters to the business. This view surfaces lapsed customers without requiring a manual spreadsheet review.
Use linked views on team pages when different people need different slices of the same data. A sales workflow can stay consistent while the views adapt to each role. See sales workflow automation for the broader process context.
Step 5: Send only relevant Gmail threads into Notion
Capturing every email is usually the wrong default. It adds noise, can multiply automation tasks, and makes the CRM harder to use. Instead, create a narrow intake rule in Gmail:
- Define the messages that belong in the CRM, such as customer replies, quote questions, or follow-up requests.
- Create a Gmail filter based on the sender, recipient, subject, or another stable condition.
- Apply a dedicated label, such as
CRM/Quote Activity. - Use the Gmail New Labeled Email trigger in Zapier so the Zap runs only when that label is applied.
- Match the message to the right contact or quote before creating a timeline entry.
A BCC address can be an alternative when the team wants to deliberately copy selected messages into the CRM. The important design choice is selective capture. Keep routine notifications, spam, and unrelated internal messages out of the workflow.
Step 6: Test the workflow before relying on it
Run a small test set before opening the workflow to the whole team:
- Submit a new Cognito quote with every important field populated.
- Submit a quote with an optional field left blank.
- Repeat a submission to test duplicate handling.
- Import a historical record and compare it with the source.
- Apply the Gmail label to a relevant thread and confirm the match.
- Check that the owner, stage, dates, and relations land in the right properties.
- Move a quote through the pipeline and confirm that views update correctly.
Document what should happen when a customer changes their email address, a quote is resubmitted, or an email cannot be matched. Those edge cases are easier to solve before the database becomes the team's daily system.
When this Cognito to Notion CRM setup fits
This approach is a good fit when Cognito already handles a complicated quote form, but the team needs better visibility after submission. It's especially useful when several people need shared ownership, pipeline views, customer relationships, and follow-up lists without giving up the existing form experience.
It's a weaker fit when the team needs a full CRM with built-in email history, advanced forecasting, or high-volume sales engagement features. In that case, Notion can still serve as an operations or reporting layer, while a dedicated CRM manages the communication-heavy parts of the sales process.
The goal isn't to force every step into one tool. Keep quote capture in Cognito, automate the handoff with Zapier, and make Notion the place where the team decides what happens next.
Get help building your Notion quote CRM
Building this setup usually breaks at the matching logic: recognizing repeat customers, keeping resubmitted quotes from creating duplicates, and routing the right Gmail threads to the right record. If you've hit that wall, book a ZoomFlow session. One of our consultants will build the database and Zaps with you live, and you'll own the workflow when we're done.
Related Posts
Salesforce to Airtable migration: CRM + production tracking playbook
A practical Salesforce to Airtable migration plan for CRM and production tracking: object audit, table mapping, status logs, dashboards, and permissions.
Migrate Make.com scenarios to n8n: audit + PRD checklist
Migrate Make.com scenarios to n8n without breaking production. Use this audit + PRD checklist to inventory modules, credentials, errors, and rebuild safely.
