Handling Timestamp Field in API URL Parameter for Incremental Sync in No-Code UI


The user is facing an issue with referencing a timestamp field in an API URL parameter for incremental sync in a no-code UI. The API requires a specific format for the parameter that is not supported by the standard low code interpolator.


building using no code option in the UI against an API that is working well except for incremental… I have a field that I can use as a timestamp field, but the way that the API wants to reference it is something like this URL param
This means that I can’t get the parameter name/value right because the standard low code interpolator wants the param to be name and then the value on the other side of the equals sign.
Anyone done anything like this on the low/no code side?

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["timestamp-field", "api", "incremental-sync", "no-code-ui", "url-parameter"]