Dapple connects to CRMs such as HubSpot, Salesforce, Pipedrive, Workbooks, Zoho and Monday via stage-based webhooks. Each time a submission moves into a stage you choose, Dapple can automatically push data to your CRM: contact details on submission, status updates at key milestones, and full application data for successful creators at the end of the process. Your CRM stays up to date throughout, without any manual exporting.
Webhooks are available on the Pro plan and will require a connector tool like Zapier in order to push through to your chosen CRM.
What does Dapple do that a CRM doesn’t?
CRMs are built for managing relationships and communications after a decision has been made. They are not designed for the submission and selection process that comes before it — building custom application forms, managing a review panel, blind scoring, and moving creators through a multi-stage pipeline.
Dapple handles intake and review. Your CRM handles everything that follows. The two tools are complementary, not competing.
What Dapple handles | What your CRM handles |
Custom application forms | Post-decision communications |
Submission intake and management | Relationship and contact management |
Review panels, scoring, and shortlisting | Marketing and email sequences |
Stage-based pipeline and bulk actions | Contracts, reporting, and post-award activity |
Creator portal and messaging | CRM dashboards and analytics |
How does the data flow from Dapple into a CRM?
Dapple’s webhooks are stage-based, meaning they fire automatically when a submission moves into a specific stage. You can set up a separate webhook on each stage, so different data gets pushed at different points in the journey.
A typical integration looks like this:
Submission received — Dapple pushes the creator’s name and email address to your CRM. A new contact is created, or an existing one is updated if the email already exists. This keeps your CRM current from the moment an application arrives.
Shortlisted (or a key review stage) — Dapple pushes a status update. Use this to tag contacts, update a contact property, or segment your CRM list by programme stage.
Successful / awarded — Dapple pushes the full submission data: all form fields, project details, and contact information. This becomes the permanent record in your CRM for everything that follows — contracts, payments, relationship management, and reporting.
You can configure as many webhook triggers as your process requires. Each project in Dapple has its own stage settings, so different programmes can push to different CRM pipelines or properties independently.
Which CRMs does this work with?
Dapple’s webhooks send data as a standard JSON payload, which means they work with any CRM that accepts incoming webhooks — either natively or via a connector tool like Zapier.
CRM | How to connect | Notes |
HubSpot | Via Zapier | Map to Contact and Deal objects. Use “Find or create contact” to avoid duplicates. |
Salesforce | Via Zapier or native webhook receiver | Map to Lead or Contact objects. Use Salesforce’s duplicate rules to handle returning creators. |
Pipedrive | Via Zapier or Pipedrive’s native webhook support | Map to Persons and Deals. Stage updates map cleanly to Pipedrive pipeline stages. |
Workbooks | Via Zapier | Map to People and Cases. Useful for arts councils and funding bodies already using Workbooks. |
Monday.com | Via Zapier or Monday’s webhook integration | Map to board items. Useful for teams using Monday as a lightweight CRM. |
For step-by-step instructions on connecting Dapple to Zapier, see How to set up webhooks for Zapier.
What data does Dapple push to the CRM?
Each webhook payload can include two types of data, which you toggle on or off per stage in the webhook settings:
Data type | What’s included | When to use it |
Creator profile | Name and email address | Submission received stage — create the contact record immediately |
Form fields | All data entered in the submission form (project title, organisation, custom questions, etc.) | Final decision stage — push the complete record once decisions are made |
Note: uploaded files and attachments are not currently included in webhook payloads. Submitted files remain accessible inside Dapple.
How do I set up a CRM integration in Dapple?
Open the relevant Project in Dapple.
Go to Project Settings → Stages.
Select the stage where you want the webhook to trigger (e.g. Received, Shortlisted, Awarded).
Open Automations → Automation Settings and click Add Automation.
Choose Trigger Webhook.
Paste your CRM or Zapier webhook URL into the Webhook URL field.
Toggle on Include Creator Profile and/or Include Form Fields as needed.
Test the webhook by moving a test submission into that stage. Use webhook.site to inspect the payload before connecting to your CRM.
Once confirmed, replace the test URL with your live CRM or Zapier endpoint.
Repeat for each stage where you want data to push.
What are the best practices for a CRM integration?
Push contact data early, full data late. Send name and email at submission received to create the contact. Send form field data only at the final decision stage to avoid cluttering your CRM with incomplete records for every applicant.
Use a deduplication rule in your CRM. If a creator applies to more than one programme, your CRM will try to create a second contact. Most CRMs (HubSpot, Salesforce, Pipedrive) can match on email address — make sure this is configured.
Test with webhook.site before going live. Inspect the raw payload to confirm all the fields you need are present and correctly labelled before mapping them in Zapier or your CRM.
Use Zapier’s Formatter step for form field data. Form fields often arrive as a single string. The Formatter by Zapier tool splits these into individual outputs so you can map each field to the correct CRM property.
Set up one webhook per stage, not one for everything. Stage-based triggers give you precise control. A single catch-all webhook is harder to map and pushes more data than most CRMs need.
Keep Dapple open for attachments. Uploaded files do not push via webhooks. If your team needs to access submitted work after a decision, they will need to return to Dapple. Plan for this in your post-decision process.