MinistryPlatform icon

MinistryPlatform

Consume MinistryPlatform API for church management data operations
Join our community

Actions6

Overview

This node interacts with the MinistryPlatform API to perform data operations on church management tables. Specifically, the Update operation for the Table resource allows users to update one or more existing records in a specified MinistryPlatform table by providing new field values.

Common scenarios include:

  • Updating contact information such as names, phone numbers, or email addresses.
  • Modifying event participant details.
  • Adjusting donation records or volunteer assignments.

Practical example:
You have a list of contacts whose last names need correction or updating. By specifying the "Contacts" table and providing an array of record objects with their unique IDs and updated fields, this node will apply those changes efficiently.

Properties

Name Meaning
Table Name The name of the MinistryPlatform table to update records in. Examples: Contacts, Participants, Events, Households, Donations.
Records A JSON array of record objects to update. Each object must contain the primary key field (e.g., Contact_ID) and the fields to update with their new values. 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 where each element corresponds to the result of updating a record. Each element contains the updated record's data as returned by the MinistryPlatform API.

  • The json output field holds the updated record objects.
  • This node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the MinistryPlatform API.
  • The node uses HTTP requests to communicate with the MinistryPlatform REST endpoints.
  • No additional external dependencies beyond the MinistryPlatform API and n8n's standard environment are required.

Troubleshooting

  • Invalid JSON format in records:
    If the "Records" property contains malformed JSON or is not an array, the node will throw an error indicating invalid JSON format.
    Resolution: Ensure the JSON is valid and represents an array of objects.

  • Missing primary key in records:
    Each record object must include the primary key field (e.g., Contact_ID) to identify which record to update. Omitting this will likely cause the API to reject the request or fail silently.
    Resolution: Include the correct primary key field for each record.

  • API authentication errors:
    If the API key credential is missing or invalid, the node will fail to authenticate.
    Resolution: Verify that the API key credential is correctly configured in n8n.

  • Network or API errors:
    Network issues or API downtime can cause failures.
    Resolution: Check network connectivity and MinistryPlatform service status.

Links and References

Discussion