Nimble Help & Support
What Nimble Triggers and Actions are Supported?
How to Get Started with Nimble
The first thing you'll need to do to get started with hooking up Nimble with Zapier and hundreds of other services is to add your Nimble Account to Zapier. Click to add a Nimble account in your Zap.
Next you will give your new Account a name or label, which is just a handy name for you to recognize within Zapier. It doesn't matter what you name it.
You should then get a pop-up window from Nimble asking you to log-in to authorize the connection between that Nimble account and Zapier.
Next you will click on the blue "Authorize" button to authorize your Nimble account.
Logging into and authorizing Nimble finishes the process! Your Nimble account is now connected to Zapier.
Popular Things To Do With Nimble
Common Problems with Nimble
Company Name is not showing up inside Nimble when creating contacts#
You should use the "Parent Company" field instead of the "Company Name" field to correctly associate your new contact with a company inside of Nimble.
When supplying a Parent Company, if it doesn't exist yet inside Nimble, it will get created.
I can't get the Person fields I need to map to my action#
If you want to map "person" fields using the New Contact trigger, you'll need to create a person in Nimble that doesn't have a company associated with them. Right now, if you create a person with a company, Nimble creates two records at the same time and sends first the person and then the company over the API, so in the editor you'll only see company record fields. Creating a sample person record with no company should get the person related fields you need to map the Zap.
I'm getting a "No valid fields data" error on create contact action.#
If you are getting this error it is likely because you do not have any name field mapped on your action. To create a contact it will need at least one of the following: first name and/or last name for a person, company name for a company.
Need More Help? - Our support team is happy to help -- send us a message