GrabPenny - new component

[michelle0927]

Resolves #17959

Summary by CodeRabbit

• New Features
  • Introduced Create Campaign action for GrabPenny, enabling users to create new campaigns with customizable parameters including task type selection, execution requirements, daily limits, and additional campaign data.
  • Enhanced task type selection with dynamically populated options for improved campaign configuration.

[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 28, 2025 6:26pm
pipedream-docs-redirect-do-not-edit	Ignored			Oct 28, 2025 6:26pm

[coderabbitai]

Walkthrough

A new GrabPenny "Create Campaign" action is introduced alongside enhancements to the app module that provide API interaction methods and task type selection, with corresponding version bump and platform dependency addition.

Changes

Cohort / File(s)	Summary
New Create Campaign Action components/grabpenny/actions/create-campaign/create-campaign.mjs	Adds action module with metadata (key, name, description, version), props for campaign configuration (grabpenny, taskTypeId, name, link, requiredExecutions, maxPerDay, miscData), and run method that maps props to API payload, handles miscData JSON parsing, and returns campaign response with summary export.
App Module Enhancements components/grabpenny/grabpenny.app.mjs	Introduces propDefinitions.taskTypeId with dynamic options via listTaskTypes method; adds public methods for _baseUrl(), _makeRequest(), listTaskTypes(), and createCampaign(); replaces placeholder authKeys with structured API interaction workflow.
Package Configuration components/grabpenny/package.json	Bumps version from 0.0.1 to 0.1.0; adds dependencies section with @pipedream/platform ^3.1.0.

Sequence Diagram

sequenceDiagram
    actor User
    participant Action as Create Campaign Action
    participant App as GrabPenny App
    participant API as GrabPenny API

    User->>Action: Invoke with props
    Note over Action: Map props to payload<br/>(camelCase → snake_case)
    Action->>Action: Parse miscData if string
    Action->>App: Call createCampaign(data)
    App->>App: Build request (_baseUrl, _makeRequest)
    App->>API: POST /campaigns
    API-->>App: Response with campaignId
    App-->>Action: Return API response
    Action->>Action: Export summary with campaignId
    Action-->>User: Return response

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Attention areas:
  • Verify miscData parsing logic handles edge cases (null, empty string, invalid JSON)
  • Confirm prop validation constraints (e.g., minimum value for requiredExecutions)
  • Review _makeRequest method implementation for error handling and HTTP status codes
  • Validate taskTypeId dynamic options mapping from API response structure

Poem

🐰 A campaign is born, with care and delight,
GrabPenny springs forth with newfound might,
Props mapped true, from camelCase to snake,
API calls swift—what wonders we'll make!
Hop-hop-hooray, our component takes flight! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The PR description provides only "Resolves #17959" and does not follow the provided description template, which requires a "WHY" section to explain the rationale for the changes. While the issue reference provides some context through the linked issue, the description itself lacks substantive explanation of why this component is being added or what problem it solves. This minimal description does not meet the template structure requirements.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Linked Issues Check	❓ Inconclusive	The PR implements the primary objective from issue #17959 by introducing a GrabPenny component with a campaign creation action. The new action module includes the required API documentation reference in its description, and the underlying GrabPenny app file provides supporting methods like createCampaign() and listTaskTypes(). However, the implemented action is named "create-campaign" based on the file structure, while the issue specifies "create-custom-social-campaign" as the action name. The functionality aligns with the requirements, but the naming discrepancy suggests the implementation may not exactly match the specified action name requirement.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "GrabPenny - new component" directly reflects the primary change in this changeset, which is the introduction of a new GrabPenny component for the platform. The title is concise, clear, and specific enough to inform a reviewer that the PR is about adding a new GrabPenny component without unnecessary verbosity or vague language. It accurately summarizes the main objective of the PR.
Out of Scope Changes Check	✅ Passed	All changes in this PR are directly related to implementing the GrabPenny component as specified in issue #17959. The new action module for creating campaigns, the updates to the GrabPenny app file with supporting methods (createCampaign, listTaskTypes, _makeRequest), and the package.json updates are all necessary infrastructure for the component implementation. No extraneous or unrelated changes are present.

✨ 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 issue-17959

---

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: 3

🧹 Nitpick comments (1)

components/grabpenny/actions/create-campaign/create-campaign.mjs (1)

38-43: Consider adding minimum value validation.

While maxPerDay is optional and documented to allow 0 for unlimited, there's no validation to prevent negative values. Consider adding min: 0 to the prop definition.

Apply this diff:

   maxPerDay: {
     type: "integer",
     label: "Max Per Day",
     description: "Maximum engagements per day (0 = unlimited)",
+    min: 0,
     optional: true,
   },

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 36a8917 and 14534cc.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• components/grabpenny/actions/create-campaign/create-campaign.mjs (1 hunks)
• components/grabpenny/grabpenny.app.mjs (1 hunks)
• components/grabpenny/package.json (2 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: pnpm publish
• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components
• GitHub Check: Lint Code Base

🔇 Additional comments (6)

components/grabpenny/grabpenny.app.mjs (3)

21-23: LGTM!

The base URL is correctly configured for the GrabPenny API v1.

---

42-54: LGTM!

The API methods are well-structured and properly delegate to _makeRequest with the correct HTTP methods and endpoints.

---

11-17: Verify GrabPenny API response structure against official documentation.

The code at line 12 assumes the API returns an object with a tasks property. However, similar components use different property names—SalesPype expects taskTypes, Clientify expects results. Without access to GrabPenny's API documentation or response examples, this assumption cannot be verified from the codebase. Confirm that the endpoint /client/tasks/ returns the expected { tasks: [...] } structure by reviewing GrabPenny's API docs or testing the component.

components/grabpenny/package.json (1)

1-18: LGTM!

The version bump to 0.1.0 is appropriate for the addition of new features, and the @pipedream/platform dependency correctly supports the axios import used in the app module.

components/grabpenny/actions/create-campaign/create-campaign.mjs (2)

1-13: LGTM!

The action metadata is well-structured and follows Pipedream conventions. The annotations appropriately indicate this is a write action with external API calls.

---

67-70: LGTM!

Response handling is well-implemented with optional chaining for safe access and a clear success message. Returning the full response provides flexibility for downstream workflows.

[jcortes]

Hi @michelle0927 lgtm! Ready for QA!