Actions55
- Webhooks Actions
- Payments Actions
- Products Actions
- Plans Actions
- Partner Referrals Actions
- Reporting Actions
- Orders Actions
- Subscriptions Actions
- Invoicing Actions
- Disputes Actions
Plans → Update Plan
AI-generatedOverview
This node provides an enhanced integration with PayPal, supporting a wide range of operations across multiple PayPal resources such as Orders, Subscriptions, Products, Plans, Invoicing, Disputes, Webhooks, Payments, Partner Referrals, and Reporting. Specifically for the Plans resource and the Update Plan operation, it allows users to update existing billing plans in their PayPal account by sending a PATCH request with the desired changes.
Common scenarios where this node is beneficial include automating subscription management workflows, updating billing plans dynamically based on business logic, or integrating PayPal plan updates into larger automation pipelines without manual intervention.
For example, you might use this node to:
- Modify pricing or billing cycles of an existing PayPal billing plan.
- Enable or disable certain features of a plan programmatically.
- Synchronize your internal product catalog updates with PayPal billing plans.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the billing plan to update. |
| Request Body | JSON-formatted string containing the fields and values to update in the billing plan. |
| Additional Options | Optional parameters including: - Environment: "Sandbox" or "Live" PayPal environment. - Page Size: Number of items per page (for list operations). - Start Time: ISO 8601 start date filter. - End Time: ISO 8601 end date filter. |
Output
The node outputs a JSON object containing:
resource: The resource type, here always"plans".operation: The operation performed, here"updatePlan".success: Boolean indicating if the operation was successful.- All fields returned by the PayPal API response for the updated plan.
creditsUsed: Number of API credits consumed by the operation (usually 1).creditsRemaining: Remaining API credits after the operation.timestamp: ISO 8601 timestamp when the operation was executed.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error message and success set to false.
Dependencies
- Requires credentials for:
- An API key credential for the external validation service ("N8N Tools API").
- A PayPal OAuth2 API credential providing an access token and environment info.
- The node uses the PayPal REST API endpoints, switching between sandbox and live URLs based on the selected environment.
- Proper configuration of these credentials in n8n is necessary for authentication and authorization.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" property is malformed, the node throws an error indicating invalid JSON. Ensure the JSON syntax is correct.
- API Validation Failure: The node first validates the requested resource and operation via an external API. If this validation fails, check that the API key credential is valid and that the resource/operation combination is supported.
- Unknown Operation or Resource: If an unsupported operation or resource is specified, the node throws an error. Verify that the operation name matches one of the supported options.
- Authentication Errors: If the PayPal OAuth2 token is invalid or expired, requests will fail. Refresh or reconfigure the PayPal credentials.
- Rate Limits or Quotas: The node tracks API credits used and remaining. Exceeding quotas may cause failures; monitor usage accordingly.