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, Events, Donations, and more. Specifically, the Delete operation on the Table resource allows users to delete an existing record from a specified MinistryPlatform table by providing the unique record ID.

Common scenarios for this node include:

  • Removing outdated or incorrect contact information.
  • Deleting event registrations or participant records that are no longer valid.
  • Cleaning up donation records or volunteer entries.

For example, if you want to delete a contact record with ID 12345 from the "Contacts" table, you would specify the table name as "Contacts" and the record ID as 12345. The node will then send a delete request to the MinistryPlatform API to remove that record.

Properties

Name Meaning
Table Name The name of the MinistryPlatform table to interact with. Common tables include: Contacts, Events, Donations, Volunteers, etc.
Record ID Unique identifier (primary key) of the record to delete. Usually formatted as <TableName>_ID (e.g., Contact_ID, Event_ID).

Output

The output is a JSON array representing the response from the MinistryPlatform API after attempting to delete the specified record. Typically, this will confirm successful deletion or provide error details if the operation failed.

No binary data is output by this node.

Example output JSON might look like:

{
  "success": true,
  "message": "Record deleted successfully"
}

or in case of failure:

{
  "error": "Record not found"
}

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 (DELETE) to communicate with the MinistryPlatform REST endpoints.

Troubleshooting

  • Invalid Record ID: If the record ID does not exist or is incorrectly formatted, the API may return an error indicating the record was not found. Verify the record ID matches the expected primary key format for the table.
  • Permission Issues: Lack of proper API credentials or insufficient permissions can cause authorization errors. Ensure the API key or token has delete permissions on the target table.
  • Network or API Errors: Connectivity issues or API downtime will result in request failures. Check network connectivity and MinistryPlatform service status.
  • JSON Parsing Errors: Although not directly applicable to Delete operation inputs, other operations require valid JSON input. For Delete, ensure the record ID is correctly provided as a string.

If the node is set to continue on fail, errors will be returned in the output JSON with an error field describing the issue.

Links and References

Discussion