jenna-mcp icon

jenna-mcp

Universal node generated from OpenAPI - satu node memuat semua endpoint

Actions60

mcp get api pengaduan

AI-generated

Overview

This node interacts with a comprehensive API for managing public complaints and related services. It supports various operations such as retrieving complaint categories, creating and updating complaints, uploading files, managing service requests, user management, and authentication. The node is useful for automating workflows involving citizen complaint handling, service requests, and administrative tasks in a municipal or community management context. For example, it can be used to fetch a list of complaints by phone number, create new complaints with detailed information, update complaint statuses, or upload related files.

Use Case Examples

  1. Fetch a paginated list of complaints filtered by phone number.
  2. Create a new complaint with title, details, location, and category.
  3. Update the status of an existing complaint.
  4. Upload a file related to a complaint.

Properties

Name Meaning
query_take Number of items to take (limit) in the query for fetching complaints.
query_page Page number for paginated results when fetching complaints.
query_search Search term to filter complaints.
query_phone Phone number to filter complaints by reporter's phone.

Output

JSON

  • ``
    • error - Indicates if there was an error in the API request.
    • message - Error or status message from the API response.
    • status - HTTP status code of the API response.
    • data - Data returned from the API, typically the requested complaint or related information.

Dependencies

  • Requires an API key credential with baseUrl and token for authentication.

Troubleshooting

  • Ensure the base URL and token credentials are correctly set; missing these will cause errors.
  • API errors return an object with error, message, status, and data fields; check these for troubleshooting.
  • Network issues or invalid endpoints may cause request failures; verify API availability and endpoint correctness.

Discussion