Actions7
- AlfaConnect Actions
- AlfaMail Actions
- NimbaSMS Actions
- Djomy Actions
Overview
The AlfaConnect node allows users to interact with the AlfaConnect API platform by making generic POST requests to specified API endpoints. This node is useful for sending data to various AlfaConnect services such as NimbaSMS, AlfaMail, Djomy, or other AlfaConnect API endpoints. Users can specify the request path, provide a JSON payload as the request body, and configure additional request options like content type, batching, SSL handling, proxy settings, and timeout. Practical applications include sending SMS messages, emails, payment requests, or any other API interaction supported by AlfaConnect.
Use Case Examples
- Sending a POST request to /v1/send-sms with a JSON body containing message details to send an SMS via NimbaSMS service.
- Posting email data to /v1/send-email endpoint to send an email using AlfaMail service.
- Submitting payment information to /v1/payment endpoint for processing via Djomy service.
Properties
| Name | Meaning |
|---|---|
| Request Path | The API endpoint path to which the POST request is sent (e.g., /v1/users, /v1/create). This defines the specific resource or action on the AlfaConnect platform. |
| Request Body (JSON) | The JSON payload sent in the body of the POST request. This contains the data relevant to the API endpoint being called. |
| Content Type | The content type of the request body, which can be either application/json or application/x-www-form-urlencoded. This affects how the request body is formatted and sent. |
| Batching | Settings to split input data into batches to throttle requests, including items per batch and interval between batches. |
| Ignore SSL Issues (Insecure) | Whether to accept responses even if SSL certificate validation fails. |
| Proxy | HTTP proxy to route the request through, including optional authentication. |
| Timeout | Time in milliseconds to wait for the server response before aborting the request. |
Output
JSON
responseData- The JSON response data returned from the AlfaConnect API after making the POST request.
Dependencies
- Requires an API key credential for AlfaConnect API authentication.
Troubleshooting
- Common issues include incorrect API endpoint paths leading to 404 errors. Verify the 'Request Path' is correct.
- Invalid JSON in the request body can cause request failures. Ensure the JSON payload is properly formatted.
- SSL certificate validation errors may occur if the server uses a self-signed or invalid certificate. Use the 'Ignore SSL Issues' option cautiously to bypass this.
- Timeout errors can happen if the server is slow or unresponsive. Adjust the 'Timeout' setting as needed.
- Proxy configuration errors may prevent requests from reaching the API. Verify proxy settings if used.