@zackbart/connecta 0.28.0 → 0.29.0

package/dist/providers/overflow/skill.generated.js

@@ -0,0 +1,8 @@
+// Generated by scripts/generate-providers.mjs; do not edit.
+export const skill = {
+    "content": "\n\n## Money, units, and status\n\nOverflow does not use one money unit, so read the unit per field:\n\n- Fields named `…InCents` are cents: deposits and their line items and\n  totals, refunds, chargebacks, and the authorize body.\n- Recurring-gift `amount` is dollars: Overflow's create and update bodies\n  say so, and its subscription reads carry the same field.\n- Contribution `amount` states no unit in Overflow's schema. Check one known\n  gift before reporting totals.\n- `status` is per asset type. A gift is final at `PAID_OUT` (cash),\n  `CONFIRMED` (manual cash, crypto), `CONTRIBUTION_RECEIVED` or `BILLED`\n  (stock), and `CONTRIBUTION_RECEIVED` (DAF). `statusBucket` filters by\n  Overflow's coarser PENDING / CONFIRMED / FAILED / CANCELED.\n- There is no funds endpoint. A gift reports its campaign and subcampaign;\n  `fundId` and `subFundId` appear only in the payment-authorize body.\n- Poll for changes with `minimumUpdatedDate`; `minimumInitiatedDate` is\n  when the donor gave.\n\n## Reconcile a deposit\n\n`list_deposits` → `get_deposit_summary` for totals → `get_deposit` for the\nline items, whose `referenceId` names the contribution, refund, or\nchargeback. Contributions also carry their `depositId`.\n\n## Donor data is sensitive\n\nGiving history and donor contact details are personal data. Reduce inside\n`execute_code` — aggregate, count, or keep ids — and return names, emails,\nphones, or addresses only when the task needs them. Lists and contributions\nalready omit contact details; `get_donor` is the deliberate lookup.\n\n## Writes go through `overflow_api_mutate`\n\nEvery Overflow write moves money or changes a donor record, so none has a\nnamed tool. Each is one approval-gated `overflow_api_mutate` call with\nOverflow's documented body:\n\n- `POST /contributions` charges a saved payment method. Its `amount`\n  states no unit; confirm it against a known gift of the same donor before\n  charging. `POST /payments/authorize` takes `amountInCents` and\n  authorizes a new method (`0` only saves it).\n- `POST /contributions/{id}/initiate-refund` (under $1,000 only).\n- `POST` / `PATCH` / `DELETE /subscriptions/{donorId}[/{subscriptionId}]`\n  creates, changes, or cancels a recurring gift. Its `amount` is dollars,\n  not cents: a $50.00 monthly gift is `amount: 50`. Cancel takes a\n  `cancellationReason` body.\n- `POST /donors`, `PATCH /donors/{id}`.\n\nResolve every id first — donors, payment methods (`list_payment_methods`),\ncampaigns, locations — and never guess one. A write that fails with HTTP 5xx\nmay still have happened: read before retrying.\n\n## Hatches, pages, and limits\n\n- `overflow_api_get` reaches the reads without a named tool: single refunds,\n  chargebacks, campaigns, locations, webhooks, and recurring gifts\n  (`/subscriptions/{donorId}/{id}`), and Tap devices, groups, and\n  destinations (`/tap/devices`, `/tap/groups`, `/tap/destinations`). Paths\n  are below `/api/v3`; array filters repeat a `name[]` query pair.\n- Lists page by number: pass `page` while `page.hasMore` is true.\n  `list_webhook_event_logs` pages by cursor instead.\n- Overflow allows 120 requests per minute per API client. This connection\n  admits the same per runtime, four at a time, which approximates rather than\n  enforces it; a `rate_limited` failure carries the wait.\n",
+    "instructionsHeading": "Nonprofit instructions",
+    "fragments": {
+        "guide_0": "\n\n## Money, units, and status\n\nOverflow does not use one money unit, so read the unit per field:\n\n- Fields named `…InCents` are cents: deposits and their line items and\n  totals, refunds, chargebacks, and the authorize body.\n- Recurring-gift `amount` is dollars: Overflow's create and update bodies\n  say so, and its subscription reads carry the same field.\n- Contribution `amount` states no unit in Overflow's schema. Check one known\n  gift before reporting totals.\n- `status` is per asset type. A gift is final at `PAID_OUT` (cash),\n  `CONFIRMED` (manual cash, crypto), `CONTRIBUTION_RECEIVED` or `BILLED`\n  (stock), and `CONTRIBUTION_RECEIVED` (DAF). `statusBucket` filters by\n  Overflow's coarser PENDING / CONFIRMED / FAILED / CANCELED.\n- There is no funds endpoint. A gift reports its campaign and subcampaign;\n  `fundId` and `subFundId` appear only in the payment-authorize body.\n- Poll for changes with `minimumUpdatedDate`; `minimumInitiatedDate` is\n  when the donor gave.\n\n## Reconcile a deposit\n\n`list_deposits` → `get_deposit_summary` for totals → `get_deposit` for the\nline items, whose `referenceId` names the contribution, refund, or\nchargeback. Contributions also carry their `depositId`.\n\n## Donor data is sensitive\n\nGiving history and donor contact details are personal data. Reduce inside\n`execute_code` — aggregate, count, or keep ids — and return names, emails,\nphones, or addresses only when the task needs them. Lists and contributions\nalready omit contact details; `get_donor` is the deliberate lookup.\n\n## Writes go through `overflow_api_mutate`\n\nEvery Overflow write moves money or changes a donor record, so none has a\nnamed tool. Each is one approval-gated `overflow_api_mutate` call with\nOverflow's documented body:\n\n- `POST /contributions` charges a saved payment method. Its `amount`\n  states no unit; confirm it against a known gift of the same donor before\n  charging. `POST /payments/authorize` takes `amountInCents` and\n  authorizes a new method (`0` only saves it).\n- `POST /contributions/{id}/initiate-refund` (under $1,000 only).\n- `POST` / `PATCH` / `DELETE /subscriptions/{donorId}[/{subscriptionId}]`\n  creates, changes, or cancels a recurring gift. Its `amount` is dollars,\n  not cents: a $50.00 monthly gift is `amount: 50`. Cancel takes a\n  `cancellationReason` body.\n- `POST /donors`, `PATCH /donors/{id}`.\n\nResolve every id first — donors, payment methods (`list_payment_methods`),\ncampaigns, locations — and never guess one. A write that fails with HTTP 5xx\nmay still have happened: read before retrying.\n\n## Hatches, pages, and limits\n\n- `overflow_api_get` reaches the reads without a named tool: single refunds,\n  chargebacks, campaigns, locations, webhooks, and recurring gifts\n  (`/subscriptions/{donorId}/{id}`), and Tap devices, groups, and\n  destinations (`/tap/devices`, `/tap/groups`, `/tap/destinations`). Paths\n  are below `/api/v3`; array filters repeat a `name[]` query pair.\n- Lists page by number: pass `page` while `page.hasMore` is true.\n  `list_webhook_event_logs` pages by cursor instead.\n- Overflow allows 120 requests per minute per API client. This connection\n  admits the same per runtime, four at a time, which approximates rather than\n  enforces it; a `rate_limited` failure carries the wait.\n"
+    }
+};

package/dist/providers/planning-center/index.d.ts

@@ -0,0 +1,59 @@
+import type { ConnectorCallAdmissionPolicy } from "../../types.js";
+/** Planning Center's REST origin. Override only for a proxy or test double. */
+export declare const PLANNING_CENTER_API_BASE_URL = "https://api.planningcenteronline.com";
+/** The products behind `/<app>/v2`, in the order their guides list them. */
+export declare const PLANNING_CENTER_APPS: readonly ["people", "services", "groups", "check-ins", "calendar", "registrations", "giving", "publishing", "webhooks", "api"];
+export type PlanningCenterApp = (typeof PLANNING_CENTER_APPS)[number];
+/**
+ * One reviewed `X-PCO-API-Version` per product, sent on every request.
+ *
+ * The header is optional, and omitting it is the trap: Planning Center then
+ * applies a per-application default chosen in a web dashboard, so behavior
+ * would follow whoever last clicked there rather than this file. Each date is
+ * the newest non-beta version in the product's documentation graph on
+ * 2026-10-05, and every projection below is written against it. A breaking
+ * change arrives as a new dated version, never inside this one, so moving a
+ * pin is a reviewed change to this table, its drift manifest, and whatever
+ * projection the version's change list touches. Notes worth keeping:
+ *
+ * - groups `2023-07-10` removed every person attribute from `Membership`, so a
+ *   membership is nameless without `include=person`.
+ * - calendar `2026-06-22` may return `BookedEvent*` stubs in place of events on
+ *   booking and conflict traversals for users without access to the event.
+ * - webhooks `2022-10-20` renamed `Subscription` to `WebhookSubscription`.
+ * - services `2018-11-01` and giving `2019-10-18` are simply the newest there is.
+ *
+ * The hatches send the same pin for the app their path names and accept a
+ * per-call `version` override for an endpoint only a newer version serves.
+ */
+export declare const PLANNING_CENTER_API_VERSIONS: Readonly<Record<PlanningCenterApp, string>>;
+export interface PlanningCenterOptions {
+    /** Which organization this is and what it should be used for. Required. */
+    purpose: string;
+    /** Human-readable display name. Defaults to "Planning Center". */
+    title?: string;
+    /** Organization-specific conventions appended to the maintained guide. */
+    instructions?: string;
+    /** Downstream auth ownership. Defaults to one shared deployment grant. */
+    authScope?: "shared" | "personal";
+    /** Connector-specific inline result limit; omit to inherit the deployment. */
+    maxResultBytes?: number;
+    /**
+     * The `User-Agent` Planning Center sees. It asks integrations to identify
+     * themselves and refuses a request without one; name your deployment and a
+     * contact. Defaults to one naming connecta.
+     */
+    userAgent?: string;
+    /** Default `per_page` for list tools. Defaults to 25; Planning Center's maximum is 100. */
+    defaultPageSize?: number;
+    /**
+     * Replaces the default per-runtime budget (100 calls per 20 seconds, five at
+     * a time). Split it when two connections share one token's user, because
+     * Planning Center meters that user once.
+     */
+    callAdmission?: ConnectorCallAdmissionPolicy;
+    /** API origin override for a proxy or test double. */
+    baseUrl?: string;
+}
+/** A maintained Planning Center Online connection over the REST API. */
+export declare const planningCenter: import("../../provider.js").ProviderFactory<PlanningCenterOptions>;