noCRM.io
The noCRM.io connector calls the rows of a prospect list, or the leads of a pipeline, in a Dialfire campaign. New leads and prospects reach Dialfire instantly. After each call the connector logs the call in noCRM, updates the fields and can turn a prospect into a lead.
For the principles shared by all connectors, see How connectors work.
Requirements
- A Dialfire account and a noCRM.io account.
- A Dialfire user with administrator rights.
- A noCRM.io user who may create API keys (usually an administrator).
Step 1: Create an API key in noCRM
In noCRM.io open the Admin panel → API keys (direct link) and create a key. You also need your organization ID: the first part of your noCRM address. If you open noCRM at https://mycompany.nocrm.io, it's mycompany.
Step 2: Connect noCRM
- Open connect.dialfire.com/connectors/nocrm and sign in to Dialfire with your administrator user.
- Enter the Organization ID and the API Key, then click validate and save.
Step 3: Link prospects or leads
- noCRM object type: choose Prospects or Leads.
- Prospects: choose the prospect list.
- Leads: choose the pipeline, and optionally steps and tags. With tags, only leads that have all of the given tags are called.
- Choose the Dialfire campaign type and a title, then click .
Step 4: Fields and phone number
Open the binding with .
- Fields: for leads, title, status, step, tags and all your lead fields. For prospects, all columns of the list.
- Phone number field: please choose one. There is no preset. Without it, the records reach Dialfire without a number and can't be called.
How the synchronization works
- New leads and prospects arrive instantly. Dialfire sets up the required webhooks in noCRM ("Send to Dialfire") itself. Leads that move to a linked step arrive instantly too.
- Changes are applied at night (between 1 and 5 am) or when you click Synchronize.
- Records that no longer match stay in the Dialfire campaign. If they should not be called any more, give them a final result in Dialfire.
What Dialfire writes to noCRM
After each call, when the contact passes the noCRM Push task:
- Call: a call entry on the lead or prospect, with the phone numbers, start and end, a link to the recording and the agent's comment. A note lists the duration and the result.
- Fields: changed values of the selected fields.
- Prospect to lead (prospect campaigns): the campaign has the extra result "Convert to lead". When the call ends with it, noCRM creates a lead from the prospect.
Appointments booked in Dialfire are not sent to noCRM.
Writing more to noCRM (advanced)
The noCRM Push task already works without changes. For special requirements open Tasks → noCRM Push → Script. The transform function lets you change the data before it is sent to noCRM.io:
- move a lead to another pipeline step:
data.step = "Qualified lead"(use the exact name of the step), - change the lead status:
data.status = "…".
Setting up Dialfire for your calls
Each binding creates a new campaign in your Dialfire account. Log in to Dialfire and:
- Set the caller ID for your outgoing calls.
- Add your agents in the Users menu.
- Check the call and recording settings of the tasks.
- Check the contact form (menu Campaign, tab Form) and make sure the fields your agents need are visible.
The campaign template already contains the noCRM Push task, which sends the results to the CRM after each call. You can adapt the task flow and the form to your needs at any time.
Need help?
New to Dialfire? Have a look at our documentation or contact our support team.
Troubleshooting
| Situation | Solution |
|---|---|
| "invalid credentials" | Check the organization ID (without https:// and .nocrm.io) and the API key. |
| "No noCRM prospect lists found" | Create a prospect list in noCRM, then reload. |
| Contacts can't be called | Choose the phone number field in the binding, then click Synchronize. |