## Issue: Nylas Connector - Incremental Sync Parameter Injection Not Working as Expected

[saicharan9676]

Hi Team,

Connector Name

Source-Nylas

Connector Version

[Please specify the version you're using]

Description

The Nylas connector is not correctly injecting incremental sync parameters into the API request URL. Despite multiple configuration attempts, the URL is not being constructed as expected for incremental syncs.

Current Behavior

The current URL being generated looks like this:
https://api.us.nylas.com/v3/grants/2dd7fd4d-75da-4c23-8490-66a2fd26d4af/messages?search_query_native=220924800

Expected Behavior

The expected URL should look like this:
https://api.us.nylas.com/v3/grants/2dd7fd4d-75da-4c23-8490-66a2fd26d4af/messages?search_query_native=from%3A+%22%7Bvisa.com%7D%22+after%3A+1234567890

Where 1234567890 is the Unix timestamp for the start of the current slice.

Steps to Reproduce

1. Configure the Nylas connector with incremental sync
2. Set up the search_query_native parameter to include both a dynamic parts (from: "{domain.com}") and (after: [timestamp])
3. Run a sync

We've tried various configurations including:

1. Using start_time_option with inject_into: request_parameter
2. Using custom parameter injection in the parameters section
3. Combining static and dynamic parts in the parameter value

None of these attempts have resulted in the correct URL construction.

The connector seems to be injecting a timestamp value into the search_query_native parameter, but it's not preserving the static part of the query or formatting it correctly.

[Natik Gadzhi (natikgadzhi)]

The easiest fix is to fork it in Connector Builder and tweak incremental settings until it works, then contribute back the fix.

[saicharan9676]

Could you help me fixing the increment sync in the connector builder? I have tried multiple approaches but none of them work. Thanks, Sai

…

On Wed, Nov 13, 2024 at 22:14 Natik Gadzhi ***@***.***> wrote: The easiest fix is to fork it in Connector Builder and tweak incremental settings until it works, then contribute back the fix. — Reply to this email directly, view it on GitHub <#48487 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJW44EPQ7FYGB4RFSAWRQ432AQIQLAVCNFSM6AAAAABRXO2IYCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMRUHA4DGOI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Airbyte Support Bot (airbyte-support-bot)]

Hi! This discussion hasn't had activity in over a year. Is this still relevant to you? If so, please reply and we'll keep it open. If we don't hear back within 14 days, we'll close this as part of our housekeeping. You can always reopen or create a new discussion later. Thanks!

---

Devin session