Invoking integrator.io APIs directly from a browser is currently unsupported (due to CORS). This is a known enhancement request, but it is not trivial to expose this capability securely (i.e. wher...
The time on the log is not meant to match the {{lastExportDateTime}} value that you see in the query parameter. The time on the log represents when the HTTP request was made, but the {{lastExportD...
In case it helps, we have a Node.js open source framework that you can use for implementing Lambda extensions. For imports specifically, it should be as simple as implementing this function signat...
The quickest way to solve this is gonna be via a support ticket where they can look at both flows and see why the data is in a different format in one vs the other. Please pass along this specific...
The only issue I can point out is that the single "record" in your preview input is actually an array, and not a single object, and this is why the script is failing. It you replace the following,...
Here are some quick screenshots. Hope this helps. “Items : Replace All Lines” = “true” “use as key to find existing lines"
Hey Paul, I just created a quick webhook listener, and also tested with Postman. Please see pics below, and hopefully this helps. P.S. in case it is not obvious, the masked '******' value in the ...
Hey Ross, how many characters are in the file download URLs? If we can work through this size limitation, then everything else should be doable. If we are in fact blocked by this size limit, then ...
I agree this is a good enhancement request for integrator.io. That said, another work around would be to simply route the raw webhook data to an S3 bucket, or FTP folder; and then have a second fl...
I am late to the game here, but it is worth noting that there is a simple work around to accomplish the desired setup: use two separate flows. The first flow should import all the data into the te...