In your API Connector call setup, you should notice a "Use as" dropdown:
Setting this "Use as" dropdown to Data will make the API call accessible within element data sources, whereas setting the dropdown to Action will make the call accessible within workflow actions. To determine the correct setting, keep in mind that 'Data' is generally used for fetching and displaying information, while 'Action' is better suited for initiating processes or sending data externally.
If you'd like the API call to be accessible in data sources and workflows, you can duplicate your call so one is set to Data while the other is set to Action. If the wrong setting is used, you may encounter errors, such as workflows failing to find the API or being prompted to reinitialize. Always double-check and reinitialize your calls when you change settings.
Other API Troubleshooting:
Handling Dynamic Data and Parameters
If your API call initializes successfully but fails during workflow execution, ensure that all dynamic data and runtime parameters are correctly passed and exist. Incorrect 'Private' parameter settings or unresolved placeholders are common causes. Tools like Postman can help validate such issues.
Configuring File Uploads in Workflows
For file upload API calls, use the FileUploader's object directly rather than a URL. Ensure that 'Send file' is enabled and that the 'Form-data' body type is configured to match the API's requirements.
Formatting Data for Backend Workflows
Failing backend API calls are often caused by JSON formatting issues or missing headers. Check your JSON structure and ensure the Content-Type header is set correctly. Use the :formatted as JSON-safe operator to handle special characters.