Airtop component fixes

[GTFalcao]

Closes #18630

Summary by CodeRabbit

• Refactor

  • Switched window creation to use a dedicated window identifier in summaries and messages for clearer tracking.
  • Simplified query action input by flattening configuration fields for more straightforward setup.
  • No public method signatures changed.

• Chores

  • Updated action versions to 0.0.2 and package version to 0.1.1.
  • General maintenance and consistency updates.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Oct 7, 2025 0:47am
pipedream-docs-redirect-do-not-edit	Ignored			Oct 7, 2025 0:47am

[coderabbitai]

Walkthrough

Updates two Airtop actions and the package version. The create-window action now uses response.windowId instead of response.id and bumps its version. The query-page action flattens certain configuration fields into the top-level payload and bumps its version. Package.json version is incremented.

Changes

Cohort / File(s)	Summary
Airtop Action: Create Window components/airtop/actions/create-window/create-window.mjs	Version 0.0.1 → 0.0.2. Replace all uses of response.id with response.windowId, including exported summary and message content construction.
Airtop Action: Query Page components/airtop/actions/query-page/query-page.mjs	Version 0.0.1 → 0.0.2. Flatten data payload: move followPaginationLinks, costThresholdCredits, timeThresholdSeconds from a nested configuration object to top-level within data.
Package Version components/airtop/package.json	Package version 0.1.0 → 0.1.1. No other changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User
  participant CreateWindow as Create-Window Action
  participant AirtopAPI as Airtop API

  User->>CreateWindow: run()
  CreateWindow->>AirtopAPI: POST /windows
  AirtopAPI-->>CreateWindow: { windowId, ... }
  CreateWindow-->>User: summary uses windowId (not id)

Loading

sequenceDiagram
  autonumber
  actor User
  participant QueryPage as Query-Page Action
  participant AirtopAPI as Airtop API

  Note over QueryPage: Payload flattened
  User->>QueryPage: run({ followPaginationLinks, costThresholdCredits, timeThresholdSeconds, ... })
  QueryPage->>AirtopAPI: POST /query with top-level fields
  AirtopAPI-->>QueryPage: { results, ... }
  QueryPage-->>User: results

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A hare taps keys with airy grace,
Window IDs hop into place.
Config burrows shallow—flat and neat,
Pages queried, swift and fleet.
Versions nudge a tiny hop,
Carrots cached—ship, don’t stop! 🥕🐇

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description only includes “Closes #18630” and does not follow the required template, as it lacks the “## WHY” section and any explanation of the motivation or impact of these changes.	Please update the description to include a “## WHY” section explaining the reasoning behind these Airtop component adjustments and any relevant context.
Title Check	❓ Inconclusive	The title “Airtop component fixes” is broadly related to the changes since it indicates that fixes were applied to the Airtop component, but it remains generic and doesn’t clearly specify the nature of the fixes made in this release.	Please refine the title to concisely describe the key changes, for example: “Use response.windowId in create-window and flatten config in query-page for Airtop component.”

✅ Passed checks (3 passed)

Check name	Status	Explanation
Linked Issues Check	✅ Passed	The changes directly update the create‐window and query‐page actions to align with the Airtop API by using response.windowId and flattening configuration fields, which fulfills the implementation objectives of the linked issue #18630.
Out of Scope Changes Check	✅ Passed	All modifications are confined to the Airtop component’s action files and package.json version bumps; there are no unrelated or extraneous changes outside the scope of supporting the Airtop API integration.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch airtop-followup-adjustments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f0ff38b and ad642a2.

📒 Files selected for processing (3)

• components/airtop/actions/create-window/create-window.mjs (2 hunks)
• components/airtop/actions/query-page/query-page.mjs (2 hunks)
• components/airtop/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components
• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base

🔇 Additional comments (4)

components/airtop/package.json (1)

3-3: LGTM!

The patch version bump is appropriate for the bug fixes applied to the action modules in this PR.

components/airtop/actions/query-page/query-page.mjs (1)

7-7: LGTM!

Version bump is appropriate for the payload structure correction.

components/airtop/actions/create-window/create-window.mjs (2)

7-7: LGTM!

Version bump is appropriate for the response property correction.

---

64-64: Approve change: use response.windowId
The Airtop create-window API returns windowId, not id, so this update is correct.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify the flattened payload structure matches the Airtop API specification.

The fields are now passed at the top level of the data object instead of nested under a configuration object. This appears to be a correction to align with the API spec.

---

🌐 Web query:

What is the correct request payload structure for the Airtop page query API endpoint? Specifically, should followPaginationLinks, costThresholdCredits, and timeThresholdSeconds be at the top level or nested under a configuration object?

💡 Result:

They belong inside the request's configuration object (i.e., nested under "configuration"), not at the top level. See the page-query and related endpoint docs showing costThresholdCredits, timeThresholdSeconds and followPaginationLinks documented as properties of the configuration object. [1][2]

Sources:
[1] Airtop "Query a page" API docs.
[2] Airtop "Query a page with pagination" / "type" docs.

---

Nest pagination and threshold fields under configuration
Move followPaginationLinks, costThresholdCredits, and timeThresholdSeconds into data.configuration in components/airtop/actions/query-page/query-page.mjs (lines 64–69) to match the Airtop API spec.

🤖 Prompt for AI Agents

In components/airtop/actions/query-page/query-page.mjs around lines 64 to 69,
the pagination and threshold fields are currently top-level in the request data;
move followPaginationLinks, costThresholdCredits, and timeThresholdSeconds under
a nested data.configuration object to match the Airtop API spec. Update the data
payload so it includes configuration: { followPaginationLinks,
costThresholdCredits, timeThresholdSeconds } while leaving prompt at the
top-level of data; ensure any callers or serialization use the new shape and run
tests or linting to confirm no other references expect the old flat fields.

[GTFalcao]

@luancazarine this was already QA'd, so please merge after approving if it's good to go

[luancazarine]

Hi @GTFalcao, LGTM! Ready for QA!