## Issue: Nylas Connector - Incremental Sync Parameter Injection Not Working as Expected #48487
Unanswered
saicharan9676
asked this question in
Connector Builder
Replies: 2 comments
-
The easiest fix is to fork it in Connector Builder and tweak incremental settings until it works, then contribute back the fix. |
Beta Was this translation helpful? Give feedback.
0 replies
-
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:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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
search_query_native
parameter to include both a dynamic parts (from: "{domain.com}"
) and (after: [timestamp]
)We've tried various configurations including:
start_time_option
withinject_into: request_parameter
parameters
sectionNone 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.Beta Was this translation helpful? Give feedback.
All reactions