STEP 1
Connect Currents and SerpApi
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Currents and SerpApi Integration
Keep Currents and SerpApi in sync by integrating their events and actions. When developer tools events happen in Currents, update the SerpApi automatically - without any line of code in visual workflow builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Currents and SerpApi
Detailed info you need to know about Currents and SerpApi integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Currents to SerpApi
Set up your Currents and SerpApi integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Currents and SerpApi nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Currents and SerpApi. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Currents and SerpApi work in WEXTL?
WEXTL exposes actions and triggers for Currents and SerpApi that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Currents triggersSerpApi actions
Currents modules
- Cancel RunCancels a run that is still in progress.
- Cancel Run by GitHub CICancels a run identified by its GitHub Actions workflow run.
- Create ActionCreates a new action that quarantines, skips, or tags matching tests.
- Create Jira IssueCreates a Jira issue from a test in a run and links it back.
- Delete ActionArchives an action so it stops applying to tests.
- Delete Project TermDeletes a tag term from a project's filter list.
- Delete RunDeletes a run and all of its associated data.
- Disable ActionDisables an action without archiving it.
- Enable ActionEnables an action that is currently disabled.
- Find RunReturns the most recent completed run matching the criteria.
- Generate Test SignatureComputes the stable signature for a test from its project, spec file, and title.
- Get ActionReturns a single action by its identifier.
- Get Affected Test ExecutionsRetrieves the executions of one affected test in a date range.
- Get InstanceReturns a single spec-file instance with its test results.
- Get ProjectReturns a single project by its identifier.
- Get Project InsightsReturns aggregated run and test metrics for a project.
- Get RunReturns a single run with its groups and spec results.
- Get Test Failure ContextReturns structured failure context for a run, a spec file, or a single test.
- Get Test ResultsRetrieves the historical executions of one test signature.
- Get WebhookReturns a single webhook by its identifier.
- Link Jira IssueLinks an existing Jira issue to a test in a run.
- List Action Test ExecutionsRetrieves the test executions where one action was applied.
- List ActionsRetrieves the actions configured for a project.
- List Affected TestsRetrieves the tests affected by actions in a date range.
- List ErrorsRetrieves errors from the Errors Explorer for a project.
- List Jira Issue TypesRetrieves the Jira issue types available for a Jira project.
- List Jira ProjectsRetrieves the Jira projects available to the connected Jira integration.
- List Project RunsRetrieves the test runs recorded for a project.
- List Project TermsRetrieves the filter terms of one kind recorded for a project.
- List ProjectsRetrieves the projects in your Currents organization.
- List Pull RequestsRetrieves the pull requests with run activity for a project.
- List Spec FilesRetrieves spec files from the Spec Files Explorer for a project.
- List TestsRetrieves tests from the Tests Explorer for a project.
- List WebhooksRetrieves the webhooks configured for a project.
- Make an API CallPerforms an arbitrary authorized API call.
- Reset RunResets failed spec files in a run so they can run again.
- Update ActionUpdates an existing action.
- Update WebhookUpdates the URL, events, headers, or label of a webhook.
- Watch EventsTriggers when a test run starts, finishes, times out, or is cancelled.
SerpApi modules
- Get Account InfoReturns account info.
- Get Facebook ProfileRuns a Facebook public profile lookup (engine=facebook_profile) by profile_id. No pagination — single profile object.
- Get Google AI OverviewResolves a Google AI Overview (engine=google_ai_overview) using a page_token captured from a prior Search Google run. No pagination — page_token IS the required input, not an offset.
- Get Google FinanceRuns a Google Finance lookup (engine=google_finance) for a stock/index/currency symbol. No pagination on this engine.
- Get Google Immersive ProductRuns a Google Immersive Product lookup (engine=google_immersive_product) via a page_token captured from a prior Google/Google Shopping search's immersive_product_page_token field. This is the vendor's live-documented replacement for the shut-down Google Product engine (google_product) — SerpApi: "Google has shutdown the Google Product service ... The Google Immersive Product API contains the same information ... and should be used instead".
- Get Google Maps DirectionsRuns a Google Maps Directions lookup (engine=google_maps_directions) between two addresses. No pagination — point-to-point routing returns a single response.
- Get Google Maps ReviewsRuns a Google Maps Reviews lookup (engine=google_maps_reviews) for a place by data_id or place_id. Pages via an opaque next_page_token.
- Get Google Play ProductRuns a Google Play product detail lookup (engine=google_play_product) by product_id + store. Reviews page via an opaque next_page_token.
- Get Google TrendsRuns a Google Trends lookup (engine=google_trends). No pagination — data_type selects timeseries/region/topic/query views of the same request.
- Get Google Trends Trending NowRuns a Google Trends Trending Now lookup (engine=google_trends_trending_now) for a region. Pages via an opaque next_page_token.
- Get LocationsReturns locations.
- Make an API CallPerforms an arbitrary authorized API call.
- Search AmazonRuns an Amazon product search (engine=amazon). Query param is k, not q; pages via page (page number, 1-based).
- Search BaiduRuns a Baidu search (engine=baidu). Pages via pn (offset) + rn (count, max 50, desktop/tablet only) — Baidu-specific param names.
- Search BingRuns a Bing web search (engine=bing). Pages via first (offset, 1-based) + count — different param names than Google.
- Search Bing ImagesRuns a Bing Images search (engine=bing_images). Pages via first (offset, 1-based) + count.
- Search Bing NewsRuns a Bing News search (engine=bing_news). Pages via first (offset, 1-based) + count.
- Search DuckDuckGoRuns a DuckDuckGo search (engine=duckduckgo). Pages via start (offset) only.
- Search EBayRuns an eBay search (engine=ebay). Query param is _nkw, not q; pages via _pgn (page number, 1-based).
- Search GoogleRuns a Google web search (engine=google) and returns organic results, answer box, and knowledge graph.
- Search Google AI ModeRuns a Google AI Mode search (engine=google_ai_mode) and returns the AI-generated answer with citations. No pagination on this engine.
- Search Google AutocompleteRuns a Google Autocomplete suggestions lookup (engine=google_autocomplete). No pagination on this engine.
- Search Google FlightsRuns a Google Flights search (engine=google_flights). No offset pagination — the vendor uses departure_token/booking_token for itinerary drill-down, out of scope for this module (use Make an API Call to chain those).
- Search Google HotelsRuns a Google Hotels search (engine=google_hotels). Pages via an opaque next_page_token, not start/num.
- Search Google ImagesRuns a Google Images search (engine=google_images). Pages via ijn (image page number, 0-99), not start/num.
- Search Google JobsRuns a Google Jobs search (engine=google_jobs). Pages via an opaque next_page_token, not start/num.
- Search Google LensRuns a Google Lens reverse-image search (engine=google_lens) for an image URL. Pages via an opaque page_token.
- Search Google LocalRuns a Google Local Pack search (engine=google_local). Pages via start (offset) only.
- Search Google MapsRuns a Google Maps places search (engine=google_maps). Pages via start (offset) only — no num/page-size parameter on this engine.
- Search Google NewsRuns a Google News search (engine=google_news). No offset pagination on this engine — SerpApi returns one results page per call.
- Search Google Play StoreRuns a Google Play Store search (engine=google_play) across apps/movies/tv/books/audiobooks. Pages via an opaque next_page_token.
- Search Google ScholarRuns a Google Scholar search (engine=google_scholar). Pages via start (offset) + num (page size).
- Search Google ShoppingRuns a Google Shopping search (engine=google_shopping) and returns shopping_results with prices and links.
- Search Google VideosRuns a Google Videos search (engine=google_videos). Pages via start (offset) + num.
- Search NaverRuns a Naver search (engine=naver). Query param is query, not q; pages via page (1-based helper for start).
- Search YahooRuns a Yahoo! search (engine=yahoo). Query param is p, not q; pages via b (offset, 1-based, +10 per page).
- Search YandexRuns a Yandex search (engine=yandex). Query param is text, not q; pages via p (0-based page number).
- Search YouTubeRuns a YouTube search (engine=youtube). Query param is search_query, not q; paging uses an opaque sp token, not an offset.
Frequently asked questions
Common questions about connecting Currents and SerpApi.
Connect your Currents and SerpApi accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Currents's "Watch Events" fires, WEXTL can "Get Account Info" in SerpApi. Currents has 1 trigger (including Watch Events); SerpApi has 38 actions (including Get Account Info, Get Facebook Profile, and Get Google AI Overview). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Currents-to-SerpApi automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Currents (or SerpApi) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Currents + SerpApi automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Currents and SerpApi integration.
- Currents and SerpApi integration source code, module specs and credentials implementation.
- Our Currents and SerpApi integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Currents and SerpApi — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Currents integration information
- SerpApi integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library