Actions13
- Check Actions
- Payment Actions
- Payee Actions
- Document Actions
Overview
This node integrates with an online payment processing suite focused on managing checks, payments, payees, and documents. Specifically, the Check - Email operation allows users to send a digital copy of a check via email. This is useful in scenarios where you want to deliver payment checks electronically rather than physically mailing them, speeding up payment delivery and improving convenience.
Practical examples include:
- Automatically emailing a check to a vendor or contractor after invoice approval.
- Sending payroll checks digitally to employees.
- Resending a check copy to a recipient upon request without reprinting or mailing.
Properties
| Name | Meaning |
|---|---|
| Check ID | The unique identifier of the check to be emailed (e.g., chk_1234567890). |
| Recipient Email | The email address where the check will be sent. Must be a valid email format. |
| Email Options | Collection of optional email settings: |
| - Subject: The subject line of the email (default: "Your check is ready"). | |
| - Message: Custom message body included in the email. | |
| - Send Copy to Self: Whether to send a copy of the email to yourself (boolean). | |
| - Priority: Email priority level; options are Normal, High, or Low (default: Normal). |
Output
The node outputs JSON data representing the result of the email operation for each input item. Typically, this includes confirmation details such as success status, any returned metadata from the API about the emailed check, or error information if the operation failed.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for the online payment processing service.
- The node depends on the external OnlineCheckWriter API to perform check-related operations including emailing.
- Proper configuration of the API credential within n8n is necessary for authentication.
Troubleshooting
- Invalid Email Address: If the recipient email does not match the required regex pattern, the node will reject the input. Ensure emails are correctly formatted.
- Missing or Invalid Check ID: Providing an incorrect or non-existent check ID will cause the API call to fail. Verify the check ID before running.
- API Authentication Errors: If the API key credential is missing, expired, or invalid, the node will throw authentication errors. Confirm the credential setup.
- Network or Service Issues: Temporary connectivity problems or service downtime may cause failures. Retrying later or checking service status can help.
- Permission Denied: The API user must have permission to email checks. Lack of permissions will result in errors.
Links and References
- OnlineCheckWriter API Documentation (example link)
- Email Validation Regex Explanation
- n8n Documentation on Creating Custom Nodes