If you receive an error code or unexpected behavior from that external service, you'll need to reach out to their support to resolve the issue, as we will be unable to troubleshoot issues in their system. Once you've isolated the issue to the third-party API, you can continue your diagnosis by following the API troubleshooting steps above, but using the API configuration documented by the third-party service instead. To help troubleshoot integration issues, we recommend users attempt to isolate the issue to either the third-party APIs or the code hosted within our Scripting extension or automation action. Troubleshooting for scriptingīoth of the above scripting options allow users to access data and workflows hosted by external (third-party) services and platforms via their APIs. Unlike the Scripting extension, this code runs server-side and would not require a CORS workaround. Built-in JavaScript libraries (like fetch) allow users to make external API calls to certain services and platforms. One of the actions available is the ability to automatically run a JavaScript code snippet, similar to the Scripting extension. Our automations allow for automatic actions based on certain Airtable event triggers. This code runs client-side and may require a CORS workaround. If you are still receiving an API error code, review our API common troubleshooting article for more information on that code. Start by verifying if the API call is configured correctly. If any part of the URL or body is incorrect, you may receive an error code or other unexpected behavior. Using a complementary tool such as Postman allows you to reproduce the API call and verify it is configured correctly by examining the response. The next step is to reproduce any error outside your application or code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |