Actions14
- Item Actions
- Project Actions
- Other Actions
Overview
This node interacts with the SwipeFlow API to manage items within projects. Specifically, the 'Reject' operation allows users to reject an item by providing the project ID, item ID, and an optional comment explaining the rejection. This is useful in content review workflows where items need to be approved or rejected based on quality or compliance criteria.
Use Case Examples
- Reject an item in a project by specifying the project ID and item ID, optionally adding a comment to explain the reason for rejection.
- Use the node to automate content moderation by rejecting items that do not meet standards.
Properties
| Name | Meaning |
|---|---|
| Item ID | The unique identifier of the item to be rejected. |
| Project Name or ID | The project containing the item to be rejected. Can be selected from a list or specified via expression. |
| Comment | Optional comment for the rejection decision, providing context or reasons for rejecting the item. |
Output
JSON
json- The response from the SwipeFlow API after rejecting the item, typically including details of the rejected item and the decision status.
Dependencies
- Requires an API key credential for authenticating with the SwipeFlow API.
Troubleshooting
- Ensure the provided project ID and item ID are correct and exist in the SwipeFlow account to avoid 'item not found' errors.
- If the API key credential is invalid or expired, authentication errors will occur; verify and update the credential as needed.
- The comment field is optional, but if used, ensure it does not contain unsupported characters that might cause API request failures.
Links
- SwipeFlow API Documentation - Reject Item - Official API documentation for rejecting an item in SwipeFlow, detailing request parameters and response structure.