DocumentationAI-generated

n8n-nodes-imis

Overview

Integrate and automate workflows with iMIS CRM for contacts, activities, memberships, and custom data, along with 3DN Workflow task management and Westpac iLink file transfers. Designed for organizations using iMIS CRM and related systems, this package provides comprehensive nodes for managing CRM records, sending emails via iMIS Howler, executing IQA queries, handling member processes, and processing workflow inputs and triggers. It also supports secure interaction with Westpac iLink for file listing, download, and deletion, enabling streamlined automation across these platforms.

Nodes & Operations

iMIS CRM

Manage core iMIS CRM data by retrieving and updating contacts and activities, including creation and modification of activity records with detailed filters and property controls.

  • Contact · Get by ID — Fetches one iMIS contact by its ID using the configured iMIS CRM credentials. Returns the contact data with iMIS $type metadata fields removed and records the ID and fetch time in item metadata.
  • Contact · Update — Update a contact in iMIS CRM by specifying the Party ID and the fields to modify.
  • Activity · Get by ID — Fetches activities for a required iMIS ID, with optional filters for activity type, activity sequence ID, transaction date range, and result limit. Returns each matching activity as an output item after removing iMIS $type metadata; if there are no matches, returns one item with a message and the ID and filters used.
  • Activity · Create — Create an iMIS activity for a party by sending the required party ID, activity type, and transaction date, with any selected additional properties. The activity type options are loaded from iMIS; dates are sent in ISO 8601 form.
  • Activity · Update — Updates an existing iMIS activity record using its sequence number, preserving all existing fields and replacing only specified properties.

iMIS CRM Trigger

Automate workflows by polling iMIS CRM for changes to contacts, activities, donations, and IQA query results, emitting new or updated records with built-in deduplication.

  • Contact · Default — Polls iMIS CRM for contacts created or updated since the last poll, fetching up to a configured maximum and applying optional deduplication.
  • Activity · Default — Polls iMIS for activities created, updated, or either since the previous poll, then emits matching records after optional deduplication. The first poll looks back the configured number of days; later polls use the time since the previous poll with a five-minute overlap.
  • Donation · Default — Polls the iMIS GiftTransaction endpoint for donations received since the previous poll, then returns new records after deduplication. On the first poll, it looks back the configured number of days.
  • IQA Query · Default — Polls an iMIS IQA query on the configured schedule and emits matching records that are new since the previous poll. On the first poll, it uses the configured lookback period; deduplication filters previously processed records by default.

iMIS Send Howler Email

Queue personalized emails through the iMIS Howler system by targeting party IDs directly or by results of IQA queries, with support for templated JSON payloads, reply-to contacts, and deduplication to prevent duplicate sends.

  • Default · Send to Party ID — Queue a Howler email for each input item’s Party ID by creating an iMIS COMMQUEUE activity with the selected Howler Definition. Optionally pass a JSON object to the template, set a Reply-To contact, and use a deduplication key to flag an already-live matching activity as DUPLICATE so it is not sent.
  • Default · Send by IQA Query — Runs an iMIS IQA query and queues a Howler email for each result row with a non-empty party ID. Each email is recorded as a COMMQUEUE activity using the selected Howler definition; an optional deduplication key is scoped to each recipient.

iMIS Member Process

Create, update, and locate member process records in the iMIS LNP_MemberProcesses table, enabling management of membership lifecycle and status associated with specific contacts.

  • Default · Add Process — Create a new member process record in the iMIS system linked to a specific contact.
  • Default · Update Process — Updates an existing iMIS member process in the LNP_MemberProcesses table, identified by Contact ID and Ordinal. Sends the selected field changes to iMIS and returns the updated record with iMIS metadata cleaned and properties flattened.
  • Default · Find Process — Finds iMIS member processes for a contact, optionally filtering by process code or ordinal. Each input item triggers a query using the required iMIS CRM API credentials.

iMIS Custom Table

Read from and write to any iMIS user-defined table or business object using composite keys or query filters, allowing flexible access and modification of custom CRM data with full support for record creation and updates.

  • Default · Get — Fetch records from an iMIS user-defined table either by a composite key to get a single record or by applying query string filters to search multiple records.
  • Default · Create — Creates a record in the specified iMIS business object or user-defined table, linked to a Party by Contact ID. Sends the supplied property name/value pairs in an authenticated POST request and returns the response as an n8n item, with iMIS type metadata and property names normalized where present.
  • Default · Update — Update an existing record in a specified iMIS custom table by its composite key, modifying one or more property key/value pairs on that record.

iMIS Group Member

Handle iMIS group memberships, including retrieval, creation, updates, and removal of memberships and their details, supporting complex relationship-type memberships like branch transfers.

  • Default · Get — Fetch group membership records for a specified group, optionally filtered by a related party ID, from the iMIS system.
  • Default · Update — Updates one existing iMIS group membership detail by retrieving the Group Member record for the supplied group and party, changing the selected detail, and posting the record back. The Group Member Detail ID must match an existing detail; the operation returns the updated membership.
  • Default · Create — Create an active iMIS group membership for a party by posting the group, party, and one membership detail to the GroupMember API. The returned record is flattened into membership identifiers, names, active status, and membership details.
  • Default · Remove — Remove a party’s membership from an iMIS group by posting a group-member record with no membership details. The operation requires the group ID and party ID for each input item.

iMIS Event Registration

Access event registration details for a party, summarizing booked functions and special table bookings to assist with event communication workflows such as confirmation emails.

  • Default · Get — Fetches an iMIS event registration for an event and party, then summarizes its booked functions and any table bookings. Adds the summary to each incoming item while preserving its existing JSON fields.

iMIS IQA Query

Run iMIS IQA queries with support for full path specification, pagination, and return of query results as discrete JSON items or aggregated collections, facilitating advanced data retrieval and reporting.

  • Default · Execute Query — Execute an iMIS IQA query by specifying its full path, optionally paginating through the results and transforming them into JSON objects. Return the results either as individual workflow items per row or as a single item containing all results and metadata.

3DN Workflow Input

Create tasks in the 3DN Workflow queue that require human input by specifying form templates, task context, priority, and callback URLs for completion notifications.

  • Default · Default — Create a human input task in the 3DN Workflow queue by selecting a form template and providing contextual task data, priority, and a callback URL to receive task completion notifications.

3DN Workflow Trigger

Receive webhook callbacks upon completion of 3DN Workflow tasks, starting workflows with optional Bearer token authentication to securely handle task results.

  • Default · Default — Receives a POST webhook when a 3DN Workflow task completes and starts the workflow with the request data. By default, it checks a Bearer API key before accepting the request; authentication can be set to None.

Westpac iLink

Interact with the Westpac iLink file transfer system to list files in the download queue, download specific files as binary, and delete files from the queue using client certificate authentication.

  • Default · List Files — Lists file names currently waiting in the Westpac iLink download queue. Uses the configured iLink client certificate and environment to make one queue request, regardless of how many input items arrive.
  • Default · Download File — Downloads the named file from the Westpac iLink download queue and returns its contents as binary data. Use the exact file name from List Files; the operation runs once for each incoming item.
  • Default · Delete File — Deletes the named file from the Westpac iLink download queue. Supply the exact file name, such as one returned by List Files; the node sends a DELETE request for each input item and returns a success record when iLink responds with HTTP 204.

Credentials

Authenticate to iMIS CRM endpoints using configured API credentials required for accessing contacts, activities, member processes, custom tables, group memberships, IQA queries, and Howler email services. Westpac iLink nodes require client certificate authentication and environment setup to securely communicate with the Qvalent REST file transfer service. 3DN Workflow Trigger optionally uses Bearer API keys for securing webhook callbacks.

Installation

Install as an n8n community node: in n8n, open Settings → Community nodes → Install and enter n8n-nodes-imis.

Links

Discussion