Merge branch 'master' into ss/gdrive-shared-drive-regression-fix

Author: michelle0927

.coderabbit.yaml

@@ -19,19 +19,19 @@ reviews:
         Review this file against the Pipedream component model described in
         .github/pipedream-component-guidelines.md.
 
+        - Verify the `version` field is incremented from its previous value and the bump
+          follows semantic versioning (see the Versioning section of the guidelines):
+          new components start at `0.0.1`; bug fixes and non-breaking refactors → patch;
+          new optional props or backwards-compatible additions → minor; removed/renamed props
+          or breaking behavior changes → major; flag any PR where the version was not bumped
+          or where the bump level seems inconsistent with the scope of the change
+        - Verify the app's `package.json` version is also bumped by the same or greater
+          semver segment as the component change
         - All prop names, method names, and local variables must use camelCase; API request
           parameter names follow the API's own convention and are the only exception
         - Props used in more than one component must be defined in the app file's
           `propDefinitions` and referenced via `propDefinition` — flag any inline prop
           definition that duplicates one already in the app file
-        - Verify `annotations` values are semantically correct (ESLint already enforces presence):
-          - `readOnlyHint: true` only when the component exclusively reads data with no side effects
-          - `destructiveHint: true` for operations that permanently delete data or irreversibly
-            overwrite it with no recovery path; update/patch/upsert operations are generally
-            `false` (reversible by another update) unless the specific endpoint does a full
-            destructive replace — when in doubt, flag and let the author decide
-          - `openWorldHint: true` for any component making external API calls (almost all);
-            `false` only for pure utility/formatting components with no HTTP requests
         - Prop `description` fields must be written for AI agent consumption:
           - Include concrete inline examples for non-obvious formats (JSON objects, IDs, dates, enums)
           - Avoid UI-centric language ("select from the dropdown", "choose from the list")
@@ -55,6 +55,14 @@ reviews:
         guidelines in .github/pipedream-action-guidelines.md.
 
         Key checks:
+        - Verify `annotations` values are semantically correct (ESLint already enforces presence):
+          - `readOnlyHint: true` only when the action exclusively reads data with no side effects
+          - `destructiveHint: true` for operations that permanently delete data or irreversibly
+            overwrite it with no recovery path; update/patch/upsert operations are generally
+            `false` (reversible by another update) unless the specific endpoint does a full
+            destructive replace — when in doubt, flag and let the author decide
+          - `openWorldHint: true` for any action making external API calls (almost all);
+            `false` only for pure utility/formatting actions with no HTTP requests
         - `run()` must call `$.export("$summary", ...)` on every successful execution path;
           summaries should be concise one-liners with key result info (record ID, name, count)
         - When `additionalProps()` or `reloadProps: true` are present, verify they are
@@ -87,6 +95,7 @@ reviews:
         guidelines in .github/pipedream-source-guidelines.md.
 
         Key checks:
+        - Source components must NOT include an `annotations` field — flag its presence as an error
         - `dedupe: "unique"` must be set at the top level of the component export
         - `$emit(data, metadata)` must include all three metadata fields: `id`, `summary`, `ts`
         - The `id` must be stable (deterministic for the same real-world event across runs) and

.github/ISSUE_TEMPLATE/app---service-integration.md

@@ -12,4 +12,4 @@ assignees: ""
 
 **Is lack of support preventing you from moving forward, or do you have a workaround?**
 
-**Are there specific actions or triggers, you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**
+**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**

.github/pipedream-component-guidelines.md

@@ -35,9 +35,8 @@ export default {
   key: "app-action-name",       // globally unique; kebab-case; prefixed with app slug
   name: "Human Readable Name",  // shown in UI and as the MCP tool name
   description: "...",           // shown in UI and used as MCP tool documentation
-  version: "0.1.0",            // semantic versioning; must be incremented on every change
+  version: "0.0.1",            // semantic versioning; must be incremented on every change
   type: "action",               // or "source"
-  annotations: { ... },        // MCP tool metadata — see Annotations section
   props: { ... },              // configuration inputs
   async run({ $ }) { ... },    // execution entry point (signature differs for sources)
 };
@@ -48,6 +47,23 @@ values are **semantically correct**, not whether properties exist.
 
 ---
 
+## Versioning
+
+Every component has a `version` field that must be incremented on every change. New
+components always start at `0.0.1`. Follow semantic versioning:
+
+| Change type | Version segment | Examples |
+|---|---|---|
+| Bug fix, copy/description tweak, refactor with no behavior change | patch (`0.0.x`) | `0.0.1` → `0.0.2` |
+| New optional prop, new output field, backwards-compatible improvement | minor (`0.x.0`) | `0.0.2` → `0.1.0` |
+| Removed or renamed prop, changed output shape, behavior change that breaks existing configs | major (`x.0.0`) | `0.1.0` → `1.0.0` |
+
+The app's `package.json` must also be bumped by the same or greater segment whenever a
+component in that app changes — patch for patch, minor for minor (or higher), major for
+major (or higher).
+
+---
+
 ## Naming Conventions
 
 All prop names, method names, and local variables must use **camelCase**. This applies
@@ -218,7 +234,10 @@ depends on an earlier selection in a way that fixed optional props cannot repres
 
 ## Annotations
 
-Every component must include an `annotations` object that communicates its runtime behavior
+**Actions only.** Source components must NOT include an `annotations` object — flag its
+presence in any source file as an error.
+
+Every action must include an `annotations` object that communicates its runtime behavior
 to AI agents and the Pipedream platform:
 
 ```javascript

.github/pull_request_template.md

@@ -1,3 +1,21 @@
-## WHY
+## Summary
+
+<!-- Add your PR description here -->
+
+
+
+## Checklist
+Please check the following items before your PR can be reviewed:
+
+### Versioning
+- [ ] All components updated in this PR had their version updated (`0.0.1` for new ones)
+- [ ] The app updated in this PR had its `package.json`'s version updated
+
+### New app
+If this is a new app, please submit [an app integration request](https://github.com/PipedreamHQ/pipedream/issues/new?template=app---service-integration.md) - the PR will only be reviewed after the app is integrated.
+- [ ] The app updated in this PR is already integrated
+
+### CodeRabbit review
+After the PR is opened, and if new changes are pushed, CodeRabbit will automatically review it. Do not 'mark as resolved' CodeRabbit's comments, but reply to them instead, whether you agree (and update the PR accordingly) or disagree.
+- [ ] I have addressed or acknowledged all of CodeRabbit's review comments
 
-<!-- author to complete -->

components/_3commas/_3commas.app.mjs

@@ -8,4 +8,4 @@ export default {
       console.log(Object.keys(this.$auth));
     },
   },
-};
+};

components/agify/README.md

@@ -0,0 +1,22 @@
+# Overview
+
+The Agify API estimates the age of a person from their first name. With Pipedream, you can use it to enrich contact records, segment users, and tailor experiences without asking customers for their age directly. The response (`name`, `age`, `count`) plugs cleanly into CRMs, marketing tools, and analytics pipelines.
+
+# Example Use Cases
+
+- **Age Diversity Research**: Run names from a public dataset — conference speaker lists, paper authors, hiring rosters — through Agify to estimate age distribution at the cohort level. Useful for diversity audits, academic representation studies, and reporting on fields where self-reported data isn't available.
+
+- **Customer Cohort Analytics**: Batch your customer or subscriber list through Agify and push aggregate age distributions to BigQuery, Snowflake, or your warehouse of choice. Build dashboards that show which products, channels, or campaigns skew which way at the population level.
+
+- **CRM Aggregate Reporting**: When new records land in Salesforce or HubSpot, route a copy through Agify on a schedule and roll the results up into group-level summaries — age bands by segment, channel, or product line — for executive reports.
+
+# Getting Started
+
+Sign up for an [Agify API key](https://agify.io) and paste it into Pipedream when connecting the account. The same key also works with [Genderize](https://pipedream.com/apps/genderize) and [Nationalize](https://pipedream.com/apps/nationalize). Free tier: 2,500 names/month.
+
+# Troubleshooting
+
+- **`401 Unauthorized`**: the API key is missing, mistyped, or has been revoked. Reconnect the account in Pipedream.
+- **`age` is `null`**: the name wasn't found in Agify's dataset. This is expected for very rare names — handle it gracefully in downstream steps.
+- **`429 Too Many Requests`**: you've hit the monthly request limit. Upgrade the Agify plan, or throttle the workflow.
+- **Batch action returns fewer results than names submitted**: requests are capped at 10 names; if you need more, split into chunks.

components/agify/actions/get-age-from-name/get-age-from-name.mjs

@@ -0,0 +1,40 @@
+import app from "../../agify.app.mjs";
+
+export default {
+  key: "agify-get-age-from-name",
+  name: "Get Age From Name",
+  description: "Estimate the age of a name. [See the documentation](https://agify.io/documentation)",
+  version: "0.0.1",
+  annotations: {
+    destructiveHint: false,
+    openWorldHint: true,
+    readOnlyHint: true,
+  },
+  type: "action",
+  props: {
+    app,
+    name: {
+      propDefinition: [
+        app,
+        "name",
+      ],
+    },
+    countryId: {
+      propDefinition: [
+        app,
+        "countryId",
+      ],
+    },
+  },
+  async run({ $ }) {
+    const response = await this.app.getAgeFromName({
+      $,
+      params: {
+        name: this.name,
+        country_id: this.countryId,
+      },
+    });
+    $.export("$summary", `Successfully sent the request. Result: ${response.age}`);
+    return response;
+  },
+};

components/agify/actions/get-age-from-names/get-age-from-names.mjs

@@ -0,0 +1,44 @@
+import { ConfigurationError } from "@pipedream/platform";
+import app from "../../agify.app.mjs";
+
+export default {
+  key: "agify-get-age-from-names",
+  name: "Get Age From Names (Batch)",
+  description: "Estimate the age of up to 10 names in a single batch request. [See the documentation](https://agify.io/documentation#batch-usage)",
+  version: "0.0.1",
+  annotations: {
+    destructiveHint: false,
+    openWorldHint: true,
+    readOnlyHint: true,
+  },
+  type: "action",
+  props: {
+    app,
+    names: {
+      propDefinition: [
+        app,
+        "names",
+      ],
+    },
+    countryId: {
+      propDefinition: [
+        app,
+        "countryId",
+      ],
+    },
+  },
+  async run({ $ }) {
+    if (this.names.length > 10) {
+      throw new ConfigurationError("Maximum 10 names per batch request");
+    }
+    const response = await this.app.getAgeFromNames({
+      $,
+      params: {
+        "name[]": this.names,
+        "country_id": this.countryId,
+      },
+    });
+    $.export("$summary", `Successfully sent the request. ${response.length} results returned.`);
+    return response;
+  },
+};

components/agify/agify.app.mjs

@@ -0,0 +1,54 @@
+import { axios } from "@pipedream/platform";
+
+export default {
+  type: "app",
+  app: "agify",
+  propDefinitions: {
+    name: {
+      type: "string",
+      label: "Name",
+      description: "Name that will be checked",
+    },
+    names: {
+      type: "string[]",
+      label: "Names",
+      description: "Up to 10 names to check in a single batch request",
+    },
+    countryId: {
+      type: "string",
+      label: "Country",
+      description: "Optional ISO 3166-1 alpha-2 country code (e.g. `US`, `GB`, `DE`) to constrain the prediction to a specific country's name distribution.",
+      optional: true,
+    },
+  },
+  methods: {
+    _baseUrl() {
+      return "https://api.agify.io";
+    },
+    async _makeRequest(opts = {}) {
+      const {
+        $ = this,
+        params,
+        ...otherOpts
+      } = opts;
+      return axios($, {
+        ...otherOpts,
+        url: this._baseUrl(),
+        params: {
+          api_key: `${this.$auth.api_key}`,
+          ...params,
+        },
+      });
+    },
+    async getAgeFromName(args = {}) {
+      return this._makeRequest({
+        ...args,
+      });
+    },
+    async getAgeFromNames(args = {}) {
+      return this._makeRequest({
+        ...args,
+      });
+    },
+  },
+};

components/agify/package.json

@@ -0,0 +1,18 @@
+{
+  "name": "@pipedream/agify",
+  "version": "0.1.0",
+  "description": "Pipedream Agify Components",
+  "main": "agify.app.mjs",
+  "keywords": [
+    "pipedream",
+    "agify"
+  ],
+  "homepage": "https://pipedream.com/apps/agify",
+  "author": "Pipedream <support@pipedream.com> (https://pipedream.com/)",
+  "publishConfig": {
+    "access": "public"
+  },
+  "dependencies": {
+    "@pipedream/platform": "^3.1.1"
+  }
+}