Integrations extend what SwiftChecklist does with the rest of your workflow. A submitted checklist can automatically create a record in your CRM. A signed agreement can be copied to your document management system. A payment confirmation can update your accounting software.
None of these connections are required to start using SwiftChecklist. The core portal and checklist workflow runs without any of them. Add integrations as you identify repetitive manual steps that happen after a submission — that is what each one is designed to remove.
Stripe — payment collection
Required if you collect payments in the portal. See Payment requests for the full Stripe setup guide.
Contact sources — Google Contacts and CSV / Excel
The Leads pipeline supports importing contacts from external sources into the Contacts staging area. Imported contacts are reviewed and approved before they enter your pipeline as active leads.
Google Contacts: Connect your Google account via Settings → Integrations → Google and sync contacts. Synced contacts appear in the staging area for review before promotion to leads. Re-sync at any time to pull in new contacts.
CSV / Excel upload: Upload a .csv or .xlsx file directly from the Leads → Contacts tab. Columns for first name, last name, email, phone, and company are auto-mapped. Duplicates and previously deleted contacts are skipped automatically.
Note: All imported contacts go through the staging area first. They are not automatically added to your pipeline. See the Leads pipeline doc for details on the staging workflow and delete memory.
File storage — Google Drive and Dropbox
Connect Google Drive or Dropbox to automatically copy uploaded client files to a designated folder in your existing document management structure.
Why this matters: Without a file storage integration, client documents live in SwiftChecklist. Your team still needs to download and organize them in your firm's document system after each submission. The integration removes that step.
Setup — Google Drive:
- Go to Settings → Integrations → Google Drive
- Click Connect with Google and authorize the connection
- Select the root folder where uploaded documents should be organized
- Configure the folder structure: by client name, by template name, or by submission date
- Test with a real or test submission to confirm files are appearing in the correct location
Setup — Dropbox: Same process via Settings → Integrations → Dropbox.
Plan note: Google Drive and Dropbox integrations are available on Pro and above.
Note on existing documents: The integration only copies documents uploaded after the connection is made. It does not retroactively copy documents from previous submissions, and files added directly in Google Drive or Dropbox do not sync back into SwiftChecklist automatically.
Slack — team notifications
Connect Slack to route checklist notifications to your team's Slack channels instead of (or in addition to) email.
Setup:
- Go to Settings → Integrations → Slack
- Click Connect with Slack and authorize the connection
- Map notification types to specific channels:
- Submission completed → #intake or #onboarding channel
- Payment received → #billing channel
- Documents uploaded → #review or practice-area-specific channel
Slack notifications include a direct link to the checklist instance. Team members can open the submission with one click from the Slack message.
Plan note: Slack integration is available on Firm and above.
Clio — legal practice management
For law firms using Clio, the Clio integration creates a new contact and matter in Clio when a checklist instance is approved in SwiftChecklist.
Available on: Firm and above plans.
What syncs:
- Client name and contact details → Clio Contact
- Matter name and description → Clio Matter
- Responsible attorney assignment → Clio Matter Responsible Attorney
- Uploaded documents → Clio Documents (attached to the relevant matter)
Setup:
- Go to Settings → Integrations → Clio
- Click Connect with Clio and authorize using your Clio credentials
- Map the SwiftChecklist fields to the corresponding Clio fields
- Configure the trigger: sync occurs when a checklist instance is Approved (recommended) or when it is Submitted
After setup, test the integration with a real or test submission to confirm the sync produces the correct Clio records.
QuickBooks — accounting software
For accounting firms, the QuickBooks integration can create a new client record in your accounting software when a checklist instance is approved.
Available on: Firm and above plans.
What syncs:
- Client name and contact details → Customer record
- Payment amount → Invoice or deposit record (where configured)
- Engagement description → Reference note on the customer record
Setup: Via Settings → Integrations → QuickBooks. The authorization flow is the same as other integrations. Field mapping is configured after authorization.
Note: These integrations create records. They do not automate billing cycles or generate invoices for ongoing work — that remains in your accounting software.
CRM and custom workflows
SwiftChecklist does not currently provide a generally available self-serve Zapier integration. If your workflow depends on a CRM sync or a custom app connection, confirm the exact supported path with support before documenting it internally for your team.
Integration troubleshooting
Connected integration is no longer syncing Integrations can disconnect when the authorizing user changes their password or revokes app access. Go to Settings → Integrations, disconnect the affected integration, and reconnect using the current credentials.
Files are not appearing in Google Drive / Dropbox Check that the connected account has write permission to the destination folder. If you recently changed the folder structure in your storage system, re-select the destination folder from the integration settings.
Clio / QuickBooks sync is creating duplicate records This usually happens when a sync trigger fires multiple times (e.g., an instance is approved, reopened, and approved again). Check the trigger configuration and set it to fire only on first approval. If duplicates already exist, merge them in the destination system.
Continue with
- Payment requests — configure Stripe for payment collection
- Add your team — configure notification routing alongside integrations