MinistryPlatform icon

MinistryPlatform

Consume MinistryPlatform API for church management data operations

Actions6

Overview

This node integrates with the MinistryPlatform API, a church management system, to perform data operations on various tables such as Contacts, Participants, Events, Households, Groups, Donations, Volunteers, and more. Specifically, the Table - Get operation retrieves a single record from a specified table using its unique record ID.

Common scenarios for this node include:

  • Fetching detailed information about a specific contact or participant by their ID.
  • Retrieving event details or donation records for reporting or processing.
  • Accessing household or group data for membership management.

For example, you might use this node to get the contact details of a person by specifying the "Contacts" table and providing the unique Contact_ID.

Properties

Name Meaning
Table Name The name of the MinistryPlatform table to interact with. Common tables include: Contacts, Participants, Events, Households, Groups, Donations, Volunteers, etc.
Record ID Unique identifier (primary key) of the record to retrieve. For most tables, this is the table name followed by "_ID" (e.g., Contact_ID, Event_ID).

Output

The output is a JSON object representing the retrieved record from the specified table. It contains all fields and their values for that particular record as stored in MinistryPlatform.

Example output structure (simplified):

{
  "Contact_ID": 123,
  "First_Name": "John",
  "Last_Name": "Doe",
  "Email_Address": "john.doe@example.com",
  ...
}

No binary data is returned by this operation.

Dependencies

  • Requires an active connection to the MinistryPlatform API.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node uses HTTP methods (GET) to fetch data from the MinistryPlatform REST endpoints.

Troubleshooting

  • Invalid Record ID: If the provided Record ID does not exist or is malformed, the API may return an error or empty response. Verify the ID format matches the expected pattern (e.g., "Contact_ID").
  • Table Name Errors: Using an incorrect or unsupported table name will cause the request to fail. Ensure the table name is spelled correctly and is one of the supported MinistryPlatform tables.
  • Authentication Issues: Missing or invalid API credentials will result in authorization errors. Confirm that the API key or token is properly set up in n8n credentials.
  • JSON Parsing Errors: Although this operation does not require JSON input parsing, other operations do. Make sure any JSON inputs are valid if switching operations.

Links and References

Discussion