I am trying to figure out how to automatically re-run at HTTP API request. I am calling an api that once I POST, takes a few minutes to complete. Therefore, I want to automatically re-run the GET request at some frequency until I get a certain response back. How can I do that?
To automatically re-run a GET request at a set frequency after a POST request, you can use a combination of our HTTP API integration and scheduled sources feature. Here's how: 1. Set up your initial POST request using the HTTP API integration. 2. Create a separate GET request using the HTTP API integration to check for the specific response. 3. Use the scheduled sources feature to run the GET request automatically: • Click the source column's title • Select your GET request source • Choose "On a schedule" under "Run this source" • Set the desired frequency (hourly, daily, weekly, or monthly) • Click "Update Source Schedule" This setup will continuously run the GET request at your specified interval until you receive the desired response. If you need help with JSON formatting or encounter any "failed to parse body" errors, please copy and paste the JSON into the chat for further troubleshooting.
That doesn’t actually solve my problem. I don’t want to re-run the entire table, just that specific http api get request column. How would I do that?
We can help you set up a scheduled column for your HTTP API GET request. Here's how: 1. In your table, click the ⛭ icon on the top right. 2. Under "Run the table", select "On a schedule". 3. Choose your preferred frequency: Day, Week, or Month. 4. Select "Only selected columns" and choose your specific HTTP API GET request column. This will automatically re-run only the selected column at your set frequency, keeping your data current without manual updates or running the entire table. Remember, you can also set up auto-update and conditional run criteria for more control over when your column runs. If you need further assistance, please let me know.
I need to have it run every 5-15 minutes. It doesn’t seem like it has that option (only days, weeks, months). Is there another option?
We can set up your HTTP API GET request column to run automatically, but the shortest interval available is hourly, and it's only for Enterprise plans. Here's how to schedule column runs: 1. Click the ⛭ icon on the top right of your table. 2. Under "Run the table", select "On a schedule". 3. Choose the frequency: Hour (Enterprise only), Day, Week, or Month. 4. Decide whether to run "All columns" or "Only selected columns". Scheduling is available across all plans, but hourly runs are exclusive to Enterprise. If you need more frequent updates, consider exploring alternative solutions within Clay. If you need further assistance, please request to talk to a person for more detailed help.
Ok. Within my HTTP API request, what do the rate limit and duration fields mean within custom rate limit? What do they control?
The rate limit and duration fields in the custom rate limit settings of your HTTP API request control how many API requests can be sent within a specific time frame. The "Request Limit" field specifies the maximum number of allowed requests, while the "Duration (in ms)" field sets the time window in milliseconds over which the request limit applies. For example, if you set a request limit of 5 and a duration of 1000 ms, it means you can send up to 5 requests per second. This feature helps prevent exceeding API rate limits set by external services.
If I put numbers into those fields, will it automatically re-run my http api request column for me over a 15 minute period?
No, entering values in the rate limit and duration fields won't automatically re-run your HTTP API request column over a 15-minute period. These fields are used to control how many API requests can be sent within a given time frame. The Request Limit specifies the maximum number of allowed requests, while the Duration (in ms) sets the time window in milliseconds. For example, if you set a Request Limit of 5 and a Duration of 1000 ms, it means 5 requests per second. This feature helps prevent exceeding API rate limits and manages the flow of requests, but it doesn't cause automatic re-runs over extended periods.