Add trigger.rs for Nango action trigger API#3714
Merged
Conversation
Co-Authored-By: yujonglee <yujonglee.dev@gmail.com>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
✅ Deploy Preview for hyprnote-storybook canceled.
|
✅ Deploy Preview for hyprnote canceled.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
trigger.rsfor Nango action trigger APISummary
Adds a new
trigger.rsmodule tocrates/nangoimplementing the POST /action/trigger Nango API endpoint.Two methods on
NangoClient:trigger_action— synchronous trigger, returnsserde_json::Valuetrigger_action_async— setsX-Async: trueheader, accepts optionalmax_retries(maps toX-Max-Retries), returns typedTriggerActionAsyncResponse { status_url, id }Follows existing crate conventions (
common_derives!macro,parse_response, header-based connection/provider params).Review & Testing Checklist for Human
cargo check -p nangofailed in CI-like env due to unrelated missing workspace member (plugins/cli2), so the new code was never actually compiled. This is the highest-priority item.serde_json::Value) is the desired ergonomic choice vs. a genericT: DeserializeOwnedparameterConnection-Id,Provider-Config-Key,X-Async,X-Max-Retries) match the actual Nango API expectationsNotes