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 for a given event record.
- Accessing donation records or volunteer profiles individually.
Practical example: You want to get the full details of a contact whose Contact_ID is 12345 to display or process in your workflow.
Properties
| Name | Meaning |
|---|---|
| Table Name | The name of the MinistryPlatform table to interact with. Examples include Contacts, Participants, Events, Households, etc. |
| Record ID | The unique identifier (primary key) of the record to retrieve from the specified table. Usually formatted as <Table>_ID. |
Output
The output is a JSON object representing the retrieved record from the specified MinistryPlatform table. The structure corresponds directly to the fields and values stored in that record within MinistryPlatform.
For example, if retrieving a Contact record, the output JSON will contain all the contact's fields such as Contact_ID, First_Name, Last_Name, Email_Address, etc., depending on what is stored in the system.
This node does not output binary data.
Dependencies
- Requires an active connection to the MinistryPlatform API.
- Requires an API authentication 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 matches one of the MinistryPlatform tables.
- API Authentication Issues: Missing or invalid API credentials will result in authorization errors. Confirm the API key/token is correctly set up in n8n credentials.
- JSON Parsing Errors: Not applicable for this operation since inputs are simple strings, but other operations involving JSON input require valid JSON formatting.
Links and References
- MinistryPlatform API Documentation (official API docs for reference)
- n8n Documentation (for general usage of custom nodes and credentials setup)