Summary
User is facing issues with the incremental feature of a Jotform connector in the Cloud Connector Builder, specifically related to how Jotform passes over filter parameters as a JSON string.
Question
Hi! Has anyone created a Jotform connector through the cloud connector builder? I’m having a little trouble with the incremental feature (it’s specific to Jotform and how they pass over filter parameters–a JSON string)
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
["jotform-connector", "incremental-feature", "cloud-connector-builder", "filter-parameters", "json-string"]
Hmm, I don’t know enough to give you a confident answer yet. The information extracts provided do not contain specific details about creating a Jotform connector using the cloud connector builder in Airbyte. However, there are some general guidelines and issues related to the incremental feature in the connector builder that might be helpful. For instance, there are open issues on GitHub discussing the need for testing incremental reads and syncs in the connector builder (source, source). There’s also a forum post discussing issues with the Incremental feature on various connectors pulling duplicate records (source). For more specific guidance on implementing incremental reads, you might find the tutorial on the Airbyte documentation helpful. It provides a step-by-step guide on how to configure a connector for incremental reads (source). If you’re still having trouble, I recommend reaching out to the Airbyte community on their forum or Slack for more specific assistance with your Jotform connector.