Overview
The node interacts with the MinistryPlatform API to perform data operations on church management tables. Specifically, the "Table - Update" operation updates one or more existing records in a specified MinistryPlatform table by sending new field values for those records.
This node is useful when you need to programmatically update multiple records in bulk within MinistryPlatform tables such as Contacts, Participants, Events, Households, Groups, Donations, Volunteers, etc. For example, you could update contact information for several people at once or modify event details in batch.
Properties
| Name | Meaning |
|---|---|
| Table Name | The name of the MinistryPlatform table where records will be updated. Common examples: Contacts, Participants, Events, etc. |
| Records | A JSON array of record objects to update. Each object must include the primary key field (e.g., Contact_ID) and fields to update. Example: [{"Contact_ID": 159, "First_Name": "John", "Last_Name": "Doe"}, {"Contact_ID": 160, "First_Name": "Jane", "Last_Name": "Smith"}] |
Output
The output is a JSON array containing the updated records returned from the MinistryPlatform API after the update operation. Each item corresponds to an input record and includes the updated field values as confirmed by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the MinistryPlatform API.
- The node uses HTTP requests to communicate with the MinistryPlatform REST endpoints.
- Proper configuration of the MinistryPlatform API credentials in n8n is necessary.
Troubleshooting
- Invalid JSON format in records: If the "Records" property contains malformed JSON or is not an array, the node will throw an error. Ensure the JSON is valid and represents an array of objects.
- Missing primary key in records: Each record object must include the unique identifier field (e.g.,
Contact_ID) to specify which record to update. Omitting this will likely cause the API to reject the request. - API errors: Errors returned from the MinistryPlatform API (such as permission issues or invalid table names) will be surfaced by the node. Verify that the table name is correct and the API credentials have sufficient permissions.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output for failed items.
Links and References
- MinistryPlatform API documentation (refer to your organization's API docs for detailed endpoint info)
- n8n documentation on creating and updating records via REST APIs