Actions60
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Deals Actions
- Webhooks Actions
- Contacts Actions
- Companies Actions
- Bussiness Types Actions
- Tags Actions
- Deal Phases Actions
- Invoices Actions
- Subscriptions Actions
- Products Actions
- Projects Actions
- Tasks Actions
- Files Actions
Overview
The "Deactivate Subscription" operation in the Teamleader node allows users to deactivate an existing subscription by specifying its unique ID. This is useful for managing subscription lifecycles, such as ending a customer's subscription service when it is no longer needed or has been cancelled.
Common scenarios include:
- Automatically deactivating subscriptions after a payment failure.
- Managing subscription status changes within automated workflows.
- Integrating subscription management with other business processes like invoicing or customer relationship management.
Example: A workflow that triggers when a customer requests cancellation and uses this operation to deactivate their subscription in Teamleader automatically.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the subscription to deactivate. This is a required string input. |
Output
The output JSON contains the response data from the Teamleader API after attempting to deactivate the subscription. Typically, this will include confirmation details about the deactivated subscription or relevant metadata returned by the API.
If the API returns multiple items (unlikely for this operation), they are flattened into the output array. If no data is returned but the request was successful, a message indicating this is included.
No binary data output is involved in this operation.
Dependencies
- Requires an active OAuth2 API credential configured for Teamleader with appropriate permissions.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the/subscriptions.deactivateoperation path. - Proper network access to Teamleader's API is necessary.
Troubleshooting
- Error: No data got returned — This indicates the API responded without expected data. Verify the subscription ID is correct and the subscription exists.
- Authentication errors — Ensure the OAuth2 credentials are valid and have not expired.
- Permission denied — The authenticated user may lack rights to deactivate subscriptions; check API permissions.
- Invalid ID format — Confirm the subscription ID is correctly formatted as a string.
- Continue on Fail option can be enabled to allow the workflow to proceed even if deactivation fails for some items.
Links and References
- Teamleader API Documentation
- Teamleader Subscriptions API section (refer to official docs for detailed parameters and responses)