MinistryPlatform icon

MinistryPlatform

Consume MinistryPlatform API for church management data operations
Join our community

Actions6

Overview

This node interacts with the MinistryPlatform API, a church management system, to perform data operations on various tables. 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 from the Contacts table.
  • Deleting event registrations or participant records that are no longer valid.
  • Cleaning up donation records or volunteer entries as needed.

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

Properties

Name Meaning
Table Name The name of the MinistryPlatform table where the record exists. Common tables: Contacts, Events, Donations, Volunteers, etc.
Record ID The 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 record. Typically, this will confirm successful deletion or provide error details if the operation failed.

No binary data is output by this operation.

Example output might be:

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

or in case of failure:

[
  {
    "error": "Record not found"
  }
]

Dependencies

  • Requires an active connection to the MinistryPlatform API via an API key credential configured in n8n.
  • The node uses HTTP methods (DELETE) to communicate with the MinistryPlatform REST endpoints.
  • Proper permissions on the MinistryPlatform side are necessary to delete records.

Troubleshooting

  • Invalid Record ID: If the record ID does not exist or is malformed, the API may return an error indicating the record was not found. Verify the record ID format and existence.
  • Permission Denied: Lack of sufficient permissions to delete records in the specified table will cause authorization errors. Ensure the API credentials have delete rights.
  • Invalid Table Name: Providing a non-existent or misspelled table name will result in API errors. Double-check the table name spelling and availability.
  • JSON Parsing Errors: Although not directly relevant to delete, other operations require valid JSON input. For delete, ensure the record ID is correctly provided as a string.
  • Network Issues: Connectivity problems can cause timeouts or failures. Check network access to the MinistryPlatform API endpoint.

Links and References

Discussion