Based on the information provided in the knowledge sources, it is currently not possible to use multiple fields as cursor fields for incremental syncs in Airbyte, including in the no-code connector builder. According to a response from an Airbyte team member in a forum discussion: [Using multiple fields as a cursor for incremental syncs > Answers](
https://discuss.airbyte.io/t/2668) > Unfortunately, based on my understanding of our normalization process, you won't be able to use multiple fields as a cursor field since normalization would break. I don't think this is possible at the moment with Airbyte but I'm happy to forward this to our product team as feedback. The current implementation of incremental syncs in Airbyte typically relies on a single cursor field, which is usually a timestamp or date field. This is evident from the documentation on incremental syncs: [Documentation > Connector-development > Connector-builder-ui > Incremental sync](
https://docs.airbyte.com/connector-development/connector-builder-ui/incremental-sync) > To use incremental syncs, the API endpoint needs to fullfil the following requirements: > - Records contain a top-level date/time field that defines when this record was last updated (the "cursor field") Given these limitations, if your source doesn't consistently contain a timestamp field in all records, you may need to consider alternative approaches. Some options could include: 1. Using a full refresh sync instead of an incremental sync. 2. If possible, adding a timestamp field to all records in your source data. 3. Exploring if there's a single field that could serve as a reliable cursor for all records. If these options are not suitable for your use case, you may want to reach out to Airbyte's support or community forums to discuss potential workarounds or to request this feature for future development.