Nimble v2

Provides integration with Nimble CRM to query contacts, deals, account fields, and pipelines, and to create, update, and delete contacts and deals.

Revision History

0.0.0.3 - Initial release.

Connection

Use this Connection to authenticate with your Nimble account.

Setup Notes

1. Generate an administrator API token in Nimble under Settings → API Token.
2. Enter the token in the Connection's ApiKey Property.
3. Test the Connection to confirm that it can retrieve the current user.
4. Select a Method and an operation template on the Nimble Node.

The Node supports cloud and local Clusters with HTTPS access to Nimble. The API destination is fixed to Nimble's service. Authentication uses the API token directly; there is no OAuth authorization or automatic token renewal.

You can list operation templates without connecting to Nimble. Loading a selected template requires a valid Connection and retrieves account-specific contact or deal field metadata when needed. Use the resulting field names and IDs when mapping your records.

Methods

Select a template to populate OperationId and the operation-specific Options, Items, and Response fields. Each Method accepts only its own supported operations.

Query

Reads contacts, individual deals, account metadata, or the current user. Contact searches are paged automatically and return one row per contact.

Create

Creates one contact or deal for each connected input item. Select post-contact or create-new-deal.

Update

Updates contacts or deals, or appends values to contact fields. Select put-contact, put-deal, or append-contact-field-values.

Delete

Deletes contacts or deals. Select delete-contact or delete-deal.

Usage Notes

• The Node handles contact paging internally. Do not supply page, per_page, or other paging controls in Options.
• Keep IDs as strings and Boolean values as booleans. Input validation does not trim strings or convert incorrect scalar types.
• String and integer collections advertised as CSV use quoted CSV. Quote values containing commas, newlines, or quotes, and double embedded quotes. Whitespace in strings is preserved. Empty text means an empty collection, "" represents one empty string. Invalid integer values are rejected. Object collections remain structured arrays.
• Contact-create tags uses Nimble's separate convention: separate tags with commas and escape a comma inside a tag with a backslash. For example, customers,best\,premium creates two tags. Contact creation allows at most five tags. Contact response tags contains objects, while tags2 uses CSV.
• Inspect Flowgear.IsSuccess on mutation results before using returned fields. Recognized per-record provider errors produce failed rows and allow later items to continue. Invalid first input records fail before a write; invalid later records produce failed rows.
• Authentication, transport, and malformed-response failures stop processing. Reads retry throttled requests at most twice. Writes are not automatically replayed. A timeout can leave the write's outcome uncertain, check Nimble before submitting it again.
• The first read or write completes when the Method starts. Later pages or input items are processed as the response stream is consumed. Multiple writes are not transactional.

Examples

Create a Person Contact

Select Create → post-contact and map an input item with this shape to Items:

{
  "type": "person",
  "fields": {
    "first name": [
      { "value": "John" }
    ],
    "last name": [
      { "value": "Doe" }
    ]
  }
}

Use the selected template to map additional fields available in your account. Check Response.Flowgear.IsSuccess before using the returned contact id.