Marketplace

Vendor-agnostic read-only daily money cockpit for a small business on QuickBooks or Xero. Binds the accounting connection through canonical core.acct.* op-steps (invoice / payment / customer search), so the same recipe runs against whichever accounting vendor you connected (the resolver dispatches each op to the bound vendor and projects its raw records to the canonical accounting fields). It surfaces open invoice pressure, what is actually overdue by due date, recent cash-in, and customers missing an email - without creating, voiding, or paying anything. Canonical accounting op-steps are read-only; every money write stays approval-gated in the accounting capability pack.

Read-only Acuity appointment review brief. It reads one appointment, its payment transactions, intake forms, appointment types, and calendars through recued-core.acuity, then asks the AI summarizer for client context, intake answers, payment status, scheduling risks, and follow-up steps. It never creates, updates, reschedules, cancels, blocks time, mutates clients, or calls arbitrary endpoints.

Read-only Acuity availability planning brief. It reads calendars, appointment types, available dates, available times, available classes, and add-ons through recued-core.acuity, then asks the AI summarizer for booking options, capacity signals, service-fit notes, and scheduling risks. It never books, reschedules, cancels, blocks time, mutates calendars, mutates appointment types, or calls arbitrary endpoints.

Scheduled read-only Acuity front-desk digest. It reads appointments, calendars, appointment types, and clients through recued-core.acuity, renders compact daily tables, and optionally sends an in-app nudge when appointments are visible. It never creates, updates, reschedules, cancels, blocks time, mutates clients, changes calendars, or calls arbitrary Acuity endpoints.

Approval-gated Apollo sequence enrollment. It searches the target sequence context, email accounts, and saved contacts, then adds explicit saved contact IDs to one existing sequence through recued-core.apollo.sequence.add_contacts with a default paused status. It does not create or update sequences, send direct emails, import contacts in bulk, enrich people, mutate stages, delete records, or call arbitrary Apollo endpoints.

Approval-gated Attio note creation. It reads target record context and existing notes, then creates one note through recued-core.attio.note.create with an explicit title and content. It does not update records, delete notes, upload files, create tasks, mutate schema, or call arbitrary Attio endpoints.

Approval-gated Attio list-entry creation. It reads list and record context, checks existing list entries, then creates one list entry through recued-core.attio.list_entry.create for an explicit record. It does not update list entries, delete list entries, create lists, mutate records, mutate schema, or call arbitrary Attio endpoints.

Approval-gated Close note workflow. It reads the target lead, creates one note activity, and returns the created note. It never uploads attachments, sends email/SMS/calls, creates tasks or opportunities, deletes notes, or calls arbitrary Close routes.

Approval-gated Greenhouse note creation. It reads the target candidate and optional application context, then creates one candidate note, email log, or activity entry through recued-core.greenhouse.note.create. It does not create candidates, move applications, change offers, mutate jobs, upload attachments, delete data, or call arbitrary Greenhouse endpoints.

Approval-gated Jotform question creation workflow. It reads one form and existing questions for context, then adds one question through recued-core.jotform.form.question.create using Jotform's documented form-encoded question[*] body shape. It does not delete questions, update arbitrary questions, mutate forms outside the single added question, create webhooks, download files, or call arbitrary endpoints.

Approval-gated Lever note creation. It reads the target opportunity and existing notes for context, then creates one note or comment through recued-core.lever.note.create. It does not create opportunities, move stages, archive, change offers, create panels or interviews, upload files, delete notes, or call arbitrary Lever endpoints.

Approval-gated Microsoft Entra group membership workflow for one user and one group. It reads the user and group for context, then calls recued-core.microsoft-entra.group.member.add with a Graph directory object reference for the user. It does not create groups, mutate group owners, change dynamic membership rules, assign directory roles, or call arbitrary Graph APIs.

Approval-gated Okta group membership add for one user and one group. It reads the user and group for context, then calls recued-core.okta.group.user.add. It does not create groups, edit group profile data, assign admin roles, mutate app assignments directly, or call arbitrary Okta APIs.

Approval-gated Outreach sequence-state creation. It reads the target prospect, target sequence, available mailboxes, and existing sequence states for context, then creates one sequence state through recued-core.outreach.sequence_state.create. It does not create or edit sequences, create sequence steps, bulk-enroll prospects, send mail, log calls, update sequence states, delete records, or call arbitrary Outreach endpoints.

Approval-gated Recurly account-note creation. It reads target account context and existing notes, then creates one account note through recued-core.recurly.account_note.create with explicit message content. It does not update accounts, mutate billing info, create subscriptions, collect invoices, create transactions, delete notes, or call arbitrary Recurly endpoints.

Approval-gated Salesloft note creation. It reads the target person and existing notes for context, then creates one person or account note through recued-core.salesloft.note.create. It does not update notes, delete notes, create tasks, enroll cadences, send emails, complete calls, or call arbitrary Salesloft endpoints.

Approval-gated Salesloft cadence membership creation. It reads the target person, target cadence, existing memberships, and visible users for context, then creates one cadence membership through recued-core.salesloft.cadence_membership.create. It does not bulk-enroll people, delete cadence memberships, import or export cadences, mutate cadence content, send emails, complete calls, or call arbitrary Salesloft endpoints.

Approval-gated Segment source-label workflow. It reads the target source and existing labels, optionally creates one label, then adds that label to the source through recued-core.segment.source.label.add. It does not replace labels, remove labels, mutate source settings, edit destinations, delete labels, change write keys, or call arbitrary Segment routes.

Approval-gated Smartsheet row add workflow. It reads one sheet for context, then calls recued-core.smartsheet.row.add with a caller-provided JSON array of Smartsheet Row objects for exactly that sheet. It does not update rows, delete rows, copy or move rows, upload attachments, send update requests, share the sheet, import files, or call arbitrary Smartsheet endpoints.

Approval-gated SurveyMonkey recipient workflow. It reads one collector and one message for context, then adds one email or SMS recipient through recued-core.surveymonkey.recipient.add. It does not bulk import recipients, use contact lists, send messages, delete recipients, or call arbitrary SurveyMonkey endpoints.

Approval-gated Squarespace inventory workflow. It reads the target variant stock, then sends exactly one inventory adjustment request with caller-supplied operations and Idempotency-Key through recued-core.squarespace. It does not edit products, fulfill orders, delete data, or call arbitrary endpoints.

Scheduled adopter for Adobe Sign agreement closure rows seeded by send-adobe-sign-agreement-with-closure. It lists only Recued-originated agreement watches, re-reads a bounded batch of Adobe Sign agreement, and closes or flags the shared row when Adobe Sign reports a configured terminal status. It can notify the owner on completion or exception status, but it never creates agreements, sends reminders, cancels agreements, updates notes, downloads binaries, opens signing URLs, configures webhooks, starts MegaSign/bulk sends, mutates templates, or calls arbitrary Adobe Sign endpoints.

Read-only Adobe Sign agreement brief. It reads one agreement, its reminders, and the API user's latest note through recued-core.adobe-sign, then asks the AI summarizer for lifecycle state, participant status, reminder history, notes, expiration risk, and concrete next steps. It never creates agreements, sends reminders, cancels, updates notes, downloads binaries, opens signing URLs, or calls arbitrary Adobe Sign endpoints.

Scheduled read-only Adobe Sign agreement digest. It reads tenant base URI context, current user context, agreements, library documents, and workflows through recued-core.adobe-sign, renders compact review tables, and optionally sends an in-app nudge when matching agreements are visible. It never creates agreements, sends reminders, cancels, updates notes, uploads transient documents, downloads binaries, opens signing or authoring URLs, mutates users/groups/templates, starts bulk sends, or calls arbitrary Adobe Sign endpoints.

Read-only Adobe Sign library document readiness review. It reads one library document plus visible workflows and recent agreements through recued-core.adobe-sign, then asks the AI summarizer for template availability, workflow fit, recent usage signals, launch risks, and next steps. It never creates or edits library documents, uploads files, opens edit views, sends agreements, or calls arbitrary Adobe Sign endpoints.

Approval-gated Maxio component allocation workflow. It reads the subscription component, previews the allocation object when provided as a single-allocation list, creates exactly one allocation through recued-core.maxio, and returns allocation history. It does not record metered usage, create subscriptions, create invoices, alter coupons, handle payment profiles, refund, void, delete, or call arbitrary Maxio endpoints.

Detects potential FHA steering violations by analyzing zip code distribution patterns across inferred buyer demographic groups. Cites 24 CFR §100.70 when risk detected. Note: Buyer names are transmitted unhashed to AI provider solely for in-memory demographic inference required by FHA analysis. Confirm your AI provider's data handling compliance.

Analyzes closed deals by win/loss reasons with metrics and AI insights. Deals without win/loss reasons are excluded from analysis. AI insights require win/loss reasons to contain no personally identifiable information (e.g., names, emails).

Evaluates deal close date validity and timeline realism with a traffic-light checklist.

Analyzes win/loss reasons for recently closed deals with AI-powered insights.

Analyzes lease contracts for missing clauses, non-standard terms, and AI-classified risks. Requires contract text in deal's 'contract_text' custom property.

Checks deal.competitors field and uses AI to scan recent notes/emails for new competitor mentions. Activities bind to your HubSpot connection via the canonical engagement.list op.

Analyzes sentiment and extracts objections from recent deal-associated emails. PII-redacted email analysis. Note: PII hashing may not catch all instances in unstructured text bodies. Activities bind to your CRM connection via the canonical engagement.list op (HubSpot engagements).

Analyzes Phase I Environmental Site Assessment documents for commercial property deals. Extracts RECs, flood zones, radon results, and classifies findings per ASTM E1527-21 with CERCLA compliance checks. Activities bind to your HubSpot connection via the canonical engagement.list op.

Reads deal data from HubSpot, sends it to your open Gemini tab for analysis, and displays the response in the sidebar. No API key needed — uses your existing Gemini account.

Compares current deal stage duration against historical averages to flag delays.

Extracts key restrictions from HOA documents (CC&Rs/bylaws) and highlights critical buyer concerns in an actionable checklist. Age restriction warnings require manual buyer eligibility verification (buyer age not available in deal data).

Validates residential lease terms against state landlord-tenant statutes with AI extraction and statutory checks. Reads the most recent NOTE on the deal as the lease document (via the canonical engagement.list op) and extracts the property's state from it; state-specific thresholds hardcoded per statutory requirements. Gracefully handles a missing lease note or unrecognized state by displaying checklist items with informative null states.

Validates real estate marketing assets against state advertising rules with statute citations and penalty warnings. Extend state_ad_rules variable beyond CA/NY defaults for additional states.

Identifies sales reps with pipeline significantly above/below team average. Flags outliers based on configurable threshold.

Verifies Residential Lead-Based Paint Hazard Reduction Act compliance for pre-1978 properties. Cites 42 U.S.C. §4852d with penalty details.

Read-only Anthropic Messages API workflow. It reads model metadata, counts tokens for explicit messages, creates one non-streaming Claude response through recued-core.anthropic.message.create, and summarizes the content and usage. It never enables tools, server web/search/fetch tools, code execution, MCP, containers, streaming, batch creation, file upload/download, managed-agent APIs, admin APIs, or arbitrary Anthropic API routes.

Scheduled read-only Anthropic operations digest. It lists Claude models, existing message batches, and beta file metadata through recued-core.anthropic, renders compact review tables, and can send an in-app notification when message batches are visible. It never creates or cancels batches, creates messages, uploads/downloads/deletes files, mutates managed agents or skills, uses admin APIs, or calls arbitrary Anthropic API routes.

Read-only Anthropic prompt readiness workflow. It reads one Claude model, counts tokens for explicit messages and optional system prompt, then summarizes context fit, cost risk signals, and model limits. It never creates a message, starts or cancels batches, uploads/downloads files, enables tools, or calls arbitrary Anthropic API routes.

Read-only Apollo contact engagement brief. It fetches one saved contact plus bounded tasks, outreach emails, sequences, and deals through recued-core.apollo, then asks core.ai.summarize for a compact seller follow-up brief. It does not enrich contacts, create contacts, add contacts to sequences, create tasks, send emails, mutate stages, delete records, or call arbitrary Apollo endpoints.

Scheduled read-only Apollo revenue operations digest. It lists bounded pages of saved contacts, accounts, sequences, tasks, deals, outreach emails, and API usage through recued-core.apollo, renders compact review tables, and optionally sends an in-app nudge when contacts are visible. It never enriches people, searches organizations, creates or updates contacts, creates sequences, sends email, mutates calls, updates stages, deletes records, or calls arbitrary Apollo endpoints.

Read-only Apollo sequence readiness brief. It searches sequences, email accounts, users, saved contacts, and outreach emails through recued-core.apollo, then asks core.ai.summarize for a compact readiness view. It does not create or update sequences, directly send emails, enrich people, bulk import contacts, mutate stages, or call arbitrary Apollo endpoints.

Approval-gated CircleCI hold-job approval workflow. It reads the workflow and workflow jobs, then approves exactly one pending approval job through recued-core.circleci.workflow.approve using the selected approval_request_id. It does not rerun workflows, cancel jobs or workflows, trigger pipelines, change schedules/triggers, mutate project settings, or call arbitrary CircleCI API routes.

Scheduled read-only digest for one Asana workspace. It reads workspace and user context, the user's task list, open My Tasks, assigned-to-me work, projects, and blocked workspace search results through recued-core.asana, renders compact tables, and can send an in-app nudge when open tasks are visible. It does not create, update, complete, delete, comment on, move, attach to, or mutate Asana resources.

Scheduled adopter for Asana task closure rows seeded by create-asana-task-with-closure. It lists only Recued-originated Asana task watches, re-reads a bounded batch of Asana task, and closes the shared row when Asana reports completion. Rows that cannot be read remain open instead of closing from cached state. It can notify the owner on completion, but it never creates, updates, completes, moves, deletes, assigns, schedules, comments on, mutates projects or sections, edits custom fields, manages dependencies, touches followers, tags, or attachments, or otherwise mutates Asana.

Read-only Attio record activity brief. It fetches one record plus bounded list-entry, open-task, note, and list evidence through recued-core.attio, then asks core.ai.summarize for a compact relationship follow-up brief. It does not update records, add records to lists, create tasks, create notes, delete notes, mutate lists, mutate schema, or call arbitrary Attio endpoints.

Scheduled adopter for Asana task comment closure rows seeded by comment-asana-task-with-closure. It lists only Recued-originated task-comment watches, re-reads a bounded batch of Asana task, and closes the shared row when Asana reports that task completed. It can notify the owner on completion, but it never creates, updates, completes, moves, deletes, attaches to, assigns, schedules, comments on, or otherwise mutates Asana tasks.

Read-only review brief for one Asana task and project. It reads task details, subtasks, stories, project metadata, project open tasks, sections, and recent status updates through recued-core.asana, then asks the AI summarizer for status, blockers, owners, and next actions. It never creates, updates, completes, comments on, moves, deletes, attaches to, or mutates Asana resources.

Read-only AssemblyAI operations workflow. It lists recent transcript jobs by optional status/date filters, tables processing state, and summarizes failures or backlog signals. It never creates transcripts, uploads files, deletes transcripts, registers webhooks, uses streaming, or calls arbitrary AssemblyAI routes.

Read-only AssemblyAI transcript review workflow. It retrieves one transcript by ID, tables chapters, highlights, sentiment, entities, and utterances when present, and summarizes readiness and insights. It never creates transcripts, uploads files, deletes transcripts, registers webhooks, uses streaming, or calls arbitrary AssemblyAI routes.

Read-only AssemblyAI transcript word-search workflow. It retrieves transcript context, searches explicit words or phrases, tables matches, and summarizes where important terms appear. It never creates transcripts, uploads files, deletes transcripts, registers webhooks, uses streaming, or calls arbitrary AssemblyAI routes.

Weighted risk score from activity staleness, close date validity, and contact engagement. Configurable weights and AI threshold.

Three-check risk assessment: activity recency, close date validity, and contact engagement status.

Analyzes coverage amount, claim history, and geographic risk factors to determine application risk level and underwriting recommendations.

Calculates no-show probability using confirmation status, contact history, and invite timing. Flags high-risk meetings.

Calculates renewal probability using usage, NPS, tickets, and engagement metrics. Generates AI retention plan when risk is high.

Approval-gated Auth0 role assignment workflow for one user. It reads the user, current role assignments, and a bounded role catalog page for context, then calls recued-core.auth0.user.role.assign with the supplied existing role IDs. It does not create roles, mutate role permissions, assign organization-scoped roles, change clients, or call arbitrary Auth0 APIs.

Read-only Attio list pipeline readiness brief. It reads list metadata, bounded list entries, open tasks, and workspace members through recued-core.attio, then asks core.ai.summarize for a compact readiness view. It does not add list entries, update list entries, create records, complete tasks, mutate lists, mutate schema, or call arbitrary Attio endpoints.

Validates deal-stage prerequisites and shows advancement readiness.

Scheduled read-only Attio relationship operations digest. It lists bounded pages of workspace metadata, objects, people, companies, deals, lists, open tasks, and notes through recued-core.attio, renders compact review tables, and optionally sends an in-app nudge when people are visible. It never updates records, upserts records, deletes records, mutates schema, completes tasks, deletes notes, creates lists, uploads files, manages comments or threads, manages webhooks, performs SCIM administration, exchanges OAuth tokens, or calls arbitrary Attio endpoints.

Audits closed deals for compliance gaps, missing documents, and anomalies. Generates AI-powered audit readiness summary.

Scheduled read-only Auth0 access governance digest. It reads a bounded page of users, roles, clients, organizations, and logs through recued-core.auth0, renders compact tables, and optionally sends an in-app nudge when matching log events are visible. It never creates or deletes users, changes passwords, mutates MFA, revokes sessions or refresh tokens, changes clients, creates roles, changes organizations, or calls arbitrary Auth0 APIs.

Read-only access review brief for one Auth0 user. It reads the user profile, tenant roles, effective permissions, organization memberships, and recent user logs through recued-core.auth0, then asks the AI summarizer for access posture, risky signals, and next steps. It never blocks users, changes roles, changes MFA, resets credentials, revokes sessions or refresh tokens, or calls arbitrary Auth0 APIs.

Scheduled read-only triage digest for one Azure DevOps project and repository. It reads project and repository metadata, active pull requests, matching WIQL work items, recent commits, and recent builds through recued-core.azure-devops, renders compact tables, and optionally sends an in-app nudge when active work is visible. It never creates or updates repositories, branches, pull requests, work items, comments, builds, releases, service hooks, or arbitrary Azure DevOps APIs.

Scheduled adopter for Azure DevOps pull request comment closure rows seeded by comment-azure-devops-pull-request-with-closure. It lists only Recued-originated pull-request-comment watches, re-reads a bounded batch of Azure DevOps pull request, and closes the shared row when Azure DevOps reports that pull request completed or abandoned. It can notify the owner on terminal pull request state, but it never creates, updates, approves, votes on, completes, abandons, deletes, resolves, comments on, edits branches for, changes reviewers on, or otherwise mutates Azure DevOps pull requests.

Read-only review brief for one Azure DevOps pull request. It reads the repository, pull request, comment threads, recent commits, and optional related builds through recued-core.azure-devops, then asks the AI summarizer for review context, open questions, risk signals, and next-review focus. It never completes, abandons, votes on, comments on, edits, or mutates the pull request.

Scheduled adopter for Azure DevOps work item comment closure rows seeded by comment-azure-devops-work-item-with-closure. It lists only Recued-originated work-item-comment watches, re-reads a bounded batch of Azure DevOps work item, and closes the shared row when Azure DevOps reports a configured terminal state such as done, closed, removed, or completed. It can notify the owner on closure, but it never creates, updates, assigns, transitions, links, attaches to, deletes, comments on, or otherwise mutates Azure DevOps work items.

Read-only BambooHR employee record brief. It fetches one employee plus selected table rows, assigned time-off policies, fields, and available table metadata through recued-core.bamboohr, then asks core.ai.summarize for a compact manager or people-ops brief. It does not update employee records, mutate tables, upload files, create time-off requests, approve or deny requests, or call arbitrary BambooHR endpoints.

Scheduled read-only BambooHR people operations digest. It lists bounded pages of employees, who's-out entries, time-off requests, time-off types, fields, and saved custom reports through recued-core.bamboohr, renders compact review tables, and optionally sends an in-app nudge when time-off requests are visible. It never creates employees, creates time-off requests, updates employee records, mutates tables, uploads files, approves or denies time off, changes policies, administers webhooks, or calls arbitrary BambooHR endpoints.

Read-only BambooHR time-off coverage brief. It fetches who's-out entries, time-off requests, time-off types, policies, and optionally one saved report through recued-core.bamboohr, then asks core.ai.summarize for absence coverage and approval-readiness guidance. It does not create, approve, deny, supersede, or cancel requests, assign policies, mutate employees, administer webhooks, or call arbitrary BambooHR endpoints.

Approval-gated Clerk user ban workflow for one user. It reads the user and active sessions for context, then calls recued-core.clerk.user.ban for exactly that user. It does not delete users, reset credentials, change MFA, revoke sessions or tokens, mutate organization roles, or call arbitrary Clerk APIs.

Action workflow over Email/Outbox. Scans likely silent outbound threads, drafts plain-text follow-ups, then sends the selected batch through the mail-send kernel ingredient. Because mail-send is the irreversible send-class boundary, attended runs route the send step through the existing approval gate. The send is the originating context, so after sending it seeds durable data.shared watch state (status watching_customer_response, loop_kind outbound_followup) keyed by thread — the same key the pressure producer uses, so it supersedes any followup_due row — and outbound-follow-up-response-watcher adopts that linkage to close the loop when the contact replies.

Read-only review brief for one BigCommerce order. It reads the order, line items, shipments, coupons, messages, available statuses, and optional customer lookup through recued-core.bigcommerce, then asks the AI summarizer for fulfillment risk, customer context, and the next concrete action. It never updates orders, products, inventory, customers, shipments, refunds, payments, checkout, carts, webhooks, scripts, or arbitrary BigCommerce endpoints.

Scheduled read-only digest for one BigCommerce Store Management API connection. It reads store metadata, catalog summary, recent orders, recently modified products, customers, coupons, and channels through recued-core.bigcommerce, renders compact commerce tables, and can send an in-app nudge when order rows are visible. It never edits products, prices, inventory, orders, shipments, refunds, payments, customers, checkout, carts, webhooks, scripts, or arbitrary BigCommerce endpoints.

Read-only Stripe customer cleanup queue. It finds customers missing email or display name so billing, support, and invoice follow-up stay usable without automatically updating Stripe records.

Read-only daily billing cockpit for a one-person company. It scans recent Stripe invoices, payments, and customers, then shows open invoice pressure, payment exceptions, and customer data gaps without sending invoices, issuing refunds, or changing Stripe records.

Read-only Stripe invoice recovery exception queue. It assumes Stripe native reminders, failed-payment emails, Smart Retries, and Billing Automations own routine recovery. It surfaces invoices that may need owner exception handling: subscription invoices whose recovery has already started and remains unpaid, and normal invoices past the configured exception window. It drafts an owner action plan without sending invoices or emails.

Read-only payment exception queue for Stripe. It separates PaymentIntents that may need customer action from statuses that should stay internal, while assuming Stripe native failed-payment emails, confirmation emails, Smart Retries, and Billing Automations own routine recovery. Customer-actionable rows should only be followed up manually when a documented exception applies.

Scheduled adopter for Bitbucket pull request comment closure rows seeded by comment-bitbucket-pull-request-with-closure. It lists only Recued-originated pull-request-comment watches, re-reads a bounded batch of Bitbucket pull request, and closes the shared row when Bitbucket reports that pull request merged, declined, or superseded. It can notify the owner on terminal pull request state, but it never creates, updates, approves, requests changes, merges, declines, deletes, resolves, comments on, runs pipelines for, or otherwise mutates Bitbucket pull requests.

Read-only review brief for one Bitbucket Cloud pull request. It reads repository metadata, pull request details, comments, commits, commit statuses, and recent pipelines through recued-core.bitbucket, then asks the AI summarizer for scope, discussion state, CI state, risks, and next actions. It never posts comments, approves, requests changes, declines, merges, edits pull requests, runs pipelines, changes branches, or calls arbitrary Bitbucket APIs.

Scheduled read-only triage digest for one Bitbucket Cloud repository. It reads the current user, workspace, repository metadata, open pull requests, matching issues, recent commits, and recent pipelines through recued-core.bitbucket, renders compact tables, and optionally sends an in-app nudge when active work is visible. It never creates or updates pull requests, issues, comments, branches, repositories, pipelines, webhooks, settings, variables, or arbitrary Bitbucket APIs.

Approval-gated Acuity calendar block workflow. It reads calendars and overlapping appointments for context, then creates one blocked-off time window through recued-core.acuity.block.create. It does not delete blocks, mutate calendars, cancel appointments, reschedule appointments, or call arbitrary endpoints.

Approval-gated Auth0 user block workflow for one user. It reads the user for context, then calls recued-core.auth0.user.block for exactly that user with blocked=true. It does not delete users, reset credentials, change MFA, revoke sessions or refresh tokens, mutate roles, or call arbitrary Auth0 APIs.

Read-only Brave Search workflow for discovering image and video results for an explicit query. It uses only the documented image and video search endpoints and does not call Brave Answers, rich callback flows, POST variants, Goggles definitions, local POI detail endpoints, or arbitrary Brave API paths.

Read-only Brave Search workflow for monitoring news results for an explicit topic, company, market, or incident. It uses the documented news search endpoint only and does not call Brave Answers, rich callbacks, POST variants, Goggles definitions, local POI detail endpoints, or arbitrary Brave API paths.

Read-only Brave Search workflow for combining web results and LLM-ready grounding context for an explicit research query. It does not call Brave Answers, rich callback flows, POST variants, Goggles definitions, local POI detail endpoints, autosuggest, spellcheck-only routes, or arbitrary Brave API paths.

Validates transaction document retention compliance against state regulations with grace period tracking. Supports CA, NY, TX, FL.

Approval-gated Browserbase context setup workflow. It creates one context upload slot for a project and summarizes the returned upload and encryption metadata. It never uploads user-data directories, updates contexts, deletes contexts, starts sessions, creates proxies, or calls arbitrary Browserbase routes.

Browserbase project usage workflow. It lists visible projects, reads one selected project, reads usage totals, and summarizes capacity, timeout, browser minutes, and proxy bytes. It never creates sessions, changes project settings, releases sessions, uploads files, or calls arbitrary Browserbase routes.

Browserbase session debugging workflow. It reads one session, live inspector URLs, logs, and rrweb recording events, then summarizes status, active pages, recent log evidence, and recording volume. It never sends browser commands, uploads files, creates resources, deletes contexts, or calls arbitrary Browserbase routes.

Approval-gated Browserbase session launch workflow. It creates one bounded browser session, returns launch status and connection URLs, and summarizes the session configuration. It never runs browser commands, configures external proxies, uploads files, installs extensions, creates certificates, or calls arbitrary Browserbase routes.

Scheduled read-only digest for one Buffer organization. It reads account context, connected channels, filtered posts, and optional daily posting limits through recued-core.buffer, renders compact tables, and can send an in-app nudge when scheduled or failed posts need attention. It does not create, edit, delete, reorder, publish, or call arbitrary Buffer GraphQL.

Read-only AI-assisted review for a Buffer content calendar. It reads account, channels, posts, ideas, and optional aggregate metrics through recued-core.buffer, then summarizes schedule health, gaps, failed posts, reusable ideas, and next publishing actions. It never creates, edits, deletes, publishes, reorders, or calls arbitrary Buffer GraphQL.

Approval-gated Acuity appointment cancellation workflow. It reads one appointment and its payments for context, then cancels that appointment through recued-core.acuity.appointment.cancel. It does not delete appointments, delete clients, mutate calendars, reschedule, block time, or call arbitrary endpoints. Acuity does not support un-canceling a canceled appointment.

Always-approval Adobe Sign cancellation workflow. It reads one agreement for context, then transitions that agreement to CANCELLED through recued-core.adobe-sign.agreement.state.update. Cancellation is irreversible for normal signing workflows. It does not delete documents, download files, mutate participants, create reminders, update notes, open authoring or signing views, or call arbitrary Adobe Sign endpoints.

Approval-gated Anthropic workflow for canceling one existing message batch. It reads the target batch first, calls recued-core.anthropic.message_batch.cancel for that explicit batch ID, and shows recent batch context. It does not create batches, delete batches, download batch results, create messages, upload/download files, mutate managed agents or skills, use admin APIs, or call arbitrary Anthropic API routes.

Approval-gated CircleCI workflow cancel workflow. It reads the workflow and current jobs for context, then cancels exactly one workflow through recued-core.circleci.workflow.cancel. It does not cancel individual jobs, rerun workflows, approve hold jobs, trigger pipelines, mutate schedules/triggers, or call arbitrary CircleCI API routes.

Approval-gated Cohere workflow for canceling one async embed job. It reads the target job first, then calls recued-core.cohere.embed_job.cancel for that explicit job ID and shows current job context. It does not create jobs, upload or delete datasets, call streaming chat/generate endpoints, use connectors, mutate fine-tuned models, or call arbitrary Cohere routes.

Always-approval Dropbox Sign cancellation workflow. It reads one signature request and signer state for context, then cancels that incomplete request through recued-core.dropbox-sign.signature_request.cancel. It does not remove access from completed requests, delete templates, download files, update signers, send reminders, bulk-cancel, or call arbitrary Dropbox Sign endpoints.

Approval-gated Firecrawl workflow for canceling one crawl job. It reads the target crawl first, calls recued-core.firecrawl.crawl.cancel for that explicit crawl ID, then lists active crawls for context. It does not start new crawls, cancel batch scrapes, mutate team settings, or call arbitrary Firecrawl API routes.

Approval-gated Mistral workflow for canceling one batch job. It reads the target batch job first, calls recued-core.mistral.batch_job.cancel for that explicit job ID, and shows current batch context. It does not create jobs, upload/download files, mutate agents, execute workflows, or call arbitrary Mistral routes.

Approval-gated Mistral workflow for canceling one fine-tuning job. It reads the target job first, calls recued-core.mistral.fine_tuning_job.cancel for that explicit job ID, and shows current fine-tuning context. It does not create, start, archive, or delete fine-tuned models, upload/download files, mutate agents, execute workflows, or call arbitrary Mistral routes.

Approval-gated Replicate workflow for canceling one running prediction. It reads the prediction first for context, then calls recued-core.replicate.prediction.cancel. It does not create predictions, start trainings, mutate models/deployments, upload/download files, reveal secrets, or call arbitrary Replicate API routes.

Scheduled adopter for Canva comment reply closure rows seeded by reply-canva-comment-with-closure. It lists only Recued-originated comment-reply watches, re-reads a bounded batch of Canva preview comment thread, and closes the shared row when Canva reports that thread resolved. It can notify the owner on resolution, but it never replies to comments, resolves or deletes comment threads, mutates designs, exports files, creates webhooks, or calls arbitrary Canva endpoints.

Read-only Canva design review brief. It reads one design, its supported export formats, and preview page metadata through recued-core.canva, then asks the AI summarizer for design context, page/export readiness, and handoff next steps. It never creates designs, exports content, updates assets, replies to comments, uploads or downloads files, or calls arbitrary Canva endpoints.

Scheduled read-only Canva creative operations digest. It reads the current user's profile/capabilities, recent designs, and brand templates through recued-core.canva, renders compact tables, and optionally sends an in-app nudge when design rows are visible. It never creates designs, exports content, updates assets, replies to comments, uploads or downloads files, moves folders, manages webhooks, uses analytics, or calls arbitrary Canva endpoints.

Approval-gated quick capture into one Google Tasks list. It creates exactly one task with a title, optional notes, and optional due timestamp through the recued-core.google-tasks task.create operation. No deletes, batch writes, hidden/deleted fields, link mutation, or arbitrary Google API calls are exposed.

Read-only Chargebee Product Catalog 2.0 readiness brief. It reads bounded pages of items, item prices, coupons, subscriptions for a selected item price, and recent catalog events through recued-core.chargebee, then summarizes checkout readiness and catalog risks. It never creates, updates, archives, deletes, or bulk mutates catalog records, coupons, subscriptions, invoices, or arbitrary Chargebee endpoints.

Read-only Chargebee customer revenue brief. It reads one customer plus bounded subscription, invoice, hosted-page, and event context through recued-core.chargebee, then summarizes revenue state and follow-up evidence. It never mutates customers, subscriptions, payment sources, invoices, hosted pages, events, or arbitrary Chargebee endpoints.

Scheduled read-only Chargebee revenue digest. It reads bounded pages of customers, subscriptions, invoices, item prices, coupons, and recent events through recued-core.chargebee, then summarizes subscription revenue operations evidence. It never mutates customers, payment sources, subscriptions, invoices, coupons, hosted pages, site settings, exports, or arbitrary Chargebee endpoints.

Tracks contract end date, calculates days until renewal, and displays status checklist with thresholds.

Verifies real estate agency disclosure compliance: signing status, correct state-mandated form, and timing relative to first showing. Cites applicable state statutes.

Validates six critical contact data points for completeness and accuracy.

Instant 5-item validation of critical contact fields on page load.

Scheduled read-only digest for one CircleCI project. It reads project metadata, recent pipelines, schedule triggers, and pipeline definitions through recued-core.circleci, renders compact tables, and can send an in-app nudge when pipeline activity is visible. It never runs pipelines, reruns workflows, cancels jobs or workflows, approves hold jobs, changes schedules/triggers, mutates project settings, reads environment variables, or calls arbitrary CircleCI API routes.

Read-only CircleCI triage brief for one workflow. It reads the workflow, its pipeline, and workflow jobs through recued-core.circleci, renders the job table, and asks core.ai.summarize for a concise failure-oriented brief. It never reruns, cancels, approves, triggers, updates schedules/triggers, reads environment variables, or calls arbitrary CircleCI API routes.

Classifies HubSpot accounts into revenue/engagement tiers with grouped table output.

Classifies accounts into revenue/engagement tiers with grouped table output.

Scheduled read-only Clerk access governance digest. It reads bounded pages of users, sessions, organizations, invitations, organization roles, and organization permissions through recued-core.clerk, renders compact review tables, and can send an in-app nudge when pending invitations are visible. It never creates or deletes users, changes passwords or MFA, creates sessions or tokens, revokes sessions or invitations, changes roles, changes domains, mutates webhooks, or calls arbitrary Clerk APIs.

Read-only access review brief for one Clerk user. It reads the user profile, active sessions, organization memberships, and organization invitations through recued-core.clerk, then asks the AI summarizer for access posture, risky signals, and next steps. It never bans users, changes organization roles, creates sessions or tokens, revokes invitations, resets credentials, mutates MFA, or calls arbitrary Clerk APIs.

Scheduled adopter for ClickUp task closure rows seeded by create-clickup-task-with-closure. It lists only Recued-originated ClickUp task watches, re-reads a bounded batch of ClickUp task, and closes the shared row when ClickUp reports a configured terminal status such as complete, completed, closed, or done. It can notify the owner on closure, but it never creates, updates, transitions, closes, deletes, attaches to, assigns, tags, checklists, time-tracks, links, webhooks, comments on, or otherwise mutates ClickUp tasks.

Scheduled adopter for ClickUp task comment closure rows seeded by comment-clickup-task-with-closure. It lists only Recued-originated task-comment watches, re-reads a bounded batch of ClickUp task, and closes the shared row when ClickUp reports a configured terminal status such as complete, completed, closed, or done. It can notify the owner on closure, but it never creates, updates, transitions, closes, deletes, attaches to, assigns, tags, checklists, time-tracks, links, webhooks, comments on, or otherwise mutates ClickUp tasks.

Read-only review brief for one ClickUp task. It reads task metadata, comments, explicit task members, time-in-status data, and attachment metadata, then asks the AI summarizer for review notes. It never changes assignment, status, permissions, comments, attachments, timers, or workspace settings.

Scheduled read-only work digest for one ClickUp Workspace. It lists a bounded page of visible tasks, open goals, and the current timer through the recued-core.clickup pack, renders compact tables, and optionally sends an in-app nudge when tasks are present. It never edits tasks, changes permissions, manages guests, uploads files, or calls arbitrary ClickUp endpoints.

Read-only Close lead activity workflow. It reads one lead plus related contacts, opportunities, tasks, and notes, then summarizes relationship state, open pipeline, activity evidence, and next follow-up. It never creates, updates, deletes, sends email/SMS/calls, exports data, or calls arbitrary Close routes.

Read-only Close revenue operations digest. It lists bounded pages of leads, opportunities, open tasks, notes, pipelines, statuses, and users, then summarizes operating load and pipeline health. It never creates, updates, deletes, exports, sends email/SMS/calls, or calls arbitrary Close routes.

Read-only review brief for one Coda doc. It reads doc metadata plus one page each of pages, tables, formulas, and controls through recued-core.coda, then asks the AI summarizer for structure, owners, live tables, control/formula signals, stale areas, and next actions. It never creates, updates, deletes, shares, publishes, exports, or calls arbitrary Coda APIs.

Read-only review brief for one Coda table. It reads table metadata, visible columns, and one page of visible rows through recued-core.coda, then asks the AI summarizer for data shape, stale signals, likely owners, notable rows, and next actions. It never creates, updates, deletes, shares, publishes, exports, or calls arbitrary Coda APIs.

Read-only Cohere embedding workflow. It lists embed-capable models, creates embeddings for explicit caller-provided text samples through recued-core.cohere.embed.create, and summarizes model/embedding readiness for search or RAG work. It never creates datasets or embed jobs, uploads files, calls streaming chat/generate endpoints, uses connectors, mutates fine-tuned models, or calls arbitrary Cohere routes.

Scheduled read-only Cohere operations digest. It checks API-key status, lists models, datasets, dataset usage, and embed jobs through recued-core.cohere, then renders compact review tables and can send an in-app notification when embed jobs are visible. It never creates or cancels jobs, uploads or deletes datasets, calls streaming chat/generate endpoints, uses connectors, mutates fine-tuned models, or calls arbitrary Cohere routes.

Read-only Cohere reranking workflow. It sends an explicit query and caller-provided document list to recued-core.cohere.rerank.create, renders relevance scores, and summarizes ranking quality for retrieval review. It never creates datasets or embed jobs, calls streaming chat/generate endpoints, uploads files, uses connectors, mutates fine-tuned models, or calls arbitrary Cohere routes.

Workflow origin for the Asana task comment closure loop. It reads one Asana task and current stories for context, creates exactly one owner-provided plain-text comment story through recued-core.asana.story.create, and when the comment succeeds it seeds durable data.shared closure state for asana-task-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, complete, move, delete, attach to, assign, schedule, or otherwise mutate Asana tasks.

Approval-gated Railway empty-service creation workflow. It reads the target project and creates exactly one service with a caller-provided name through recued-core.railway. It does not connect repositories, deploy code, mutate variables, create domains or volumes, delete resources, or call arbitrary Railway GraphQL.

Workflow origin for the Azure DevOps pull request comment closure loop. It reads one Azure DevOps repository, pull request, and current thread comments for context, creates exactly one owner-provided top-level thread comment through recued-core.azure-devops.pull_request.thread.create, and when the thread succeeds it seeds durable data.shared closure state for azure-devops-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not complete, abandon, approve, vote on, edit, retarget, assign reviewers to, delete, or otherwise mutate Azure DevOps pull requests.

Approval-gated Azure DevOps pull request comment workflow. It reads the target repository and pull request for context, then creates exactly one top-level pull request thread comment through recued-core.azure-devops when comment text is present. It does not complete, abandon, approve, vote on, edit, retarget, assign reviewers to, delete, or otherwise mutate the pull request.

Workflow origin for the Azure DevOps work item comment closure loop. It reads one Azure DevOps work item and current comments for context, creates exactly one owner-provided comment through recued-core.azure-devops.work_item.comment.add, and when the comment succeeds it seeds durable data.shared closure state for azure-devops-work-item-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, assign, transition, link, attach to, delete, or otherwise mutate Azure DevOps work items.

Approval-gated Azure DevOps work item comment workflow. It reads the target work item and existing comments for context, then adds exactly one work item comment through recued-core.azure-devops when comment text is present. It does not create, update, assign, transition, link, attach to, delete, or otherwise mutate the work item.

Workflow origin for the Bitbucket pull request comment closure loop. It reads one Bitbucket pull request and current comments for context, creates exactly one owner-provided top-level comment through recued-core.bitbucket.pull_request.comment.create, and when the comment succeeds it seeds durable data.shared closure state for bitbucket-pull-request-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not approve, request changes, merge, decline, edit, resolve, delete, update pull request metadata, run pipelines, or otherwise mutate Bitbucket pull requests.

Approval-gated Bitbucket Cloud pull request comment workflow. It reads the target repository and pull request for context, then creates exactly one top-level pull request comment through recued-core.bitbucket when comment text is present. It does not approve, request changes, decline, merge, edit comments, delete comments, resolve threads, change pull request metadata, run pipelines, or call arbitrary Bitbucket APIs.

Workflow origin for the ClickUp task comment closure loop. It reads one ClickUp task and current comments for context, creates exactly one owner-provided task comment through recued-core.clickup.task.comment.create, and when the comment succeeds it seeds durable data.shared closure state for clickup-task-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, transition, close, delete, attach to, assign, tag, checklist, time-track, link, webhook, or otherwise mutate ClickUp tasks.

Workflow origin for the GitHub issue comment closure loop. It reads one GitHub issue and current comments for context, creates exactly one owner-provided Markdown comment through recued-core.github-pack.issue.comment, and when the comment succeeds it seeds durable data.shared closure state for github-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, transfer, label, assign, lock, or otherwise mutate GitHub issues. It skips pull-request-shaped issue reads so code review remains on GitHub's pull request surfaces.

Workflow origin for the GitLab issue note closure loop. It reads one GitLab issue and current comment notes for context, creates exactly one owner-provided public note through recued-core.gitlab.issue.note.create, and when the note succeeds it seeds durable data.shared closure state for gitlab-issue-note-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, close, reopen, delete, move, label, assign, or otherwise mutate GitLab issues.

Workflow origin for the Google Drive file comment closure loop. It reads one Drive file and its current comments for context, creates exactly one owner-provided top-level file comment through recued-core.gdrive.file.comment.create, and when the comment succeeds it seeds durable data.shared closure state for google-drive-file-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not edit or delete comments, resolve comment threads, change file permissions, mutate document body content, download files, move files, create folders, configure Drive notifications, or call arbitrary Google Drive endpoints.

Workflow origin for the Jira issue comment closure loop. It reads one Jira issue and current comments for context, creates exactly one owner-provided Atlassian Document Format comment through recued-core.jira.comment.add, and when the comment succeeds it seeds durable data.shared closure state for jira-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, transition, assign, delete, attach to, link, watch, vote on, or otherwise mutate Jira issues.

Workflow origin for the Linear issue comment closure loop. It reads one Linear issue and current comments for context, creates exactly one owner-provided Markdown comment through recued-core.linear.comment.create, and when the comment succeeds it seeds durable data.shared closure state for linear-issue-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, move, cancel, complete, delete, archive, assign, label, subscribe to, or otherwise mutate Linear issues.

Workflow origin for the monday.com item update closure loop. It reads one monday.com board, item, and current item updates for context, creates exactly one owner-provided item update through recued-core.monday.update.create, and when the update succeeds it seeds durable data.shared closure state for monday-item-update-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create items, edit column values, move, archive, delete, restructure, upload to, invite users to, automate, notify from, or otherwise mutate monday.com items beyond the owner-approved update/comment.

Workflow origin for the Notion page comment closure loop. It reads one Notion page and one configured status property, reads current unresolved comments for context, creates exactly one owner-provided page comment through recued-core.notion.comment.create, and when the comment succeeds it seeds durable data.shared closure state for notion-page-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, trash, move, lock, template, append blocks to, update to-do blocks on, edit comments on, delete from, export, or otherwise mutate Notion pages.

Approval-gated Smartsheet discussion reply workflow. It reads one discussion with comments for context, then adds one text-only comment through recued-core.smartsheet.discussion.comment.add. It does not create attachments, update or delete comments, share sheets, send email/update requests, create automations, or call arbitrary Smartsheet endpoints.

Approval-gated Segment governance workflow. It reads the target source, tracking plan, existing tracking-plan rules, and currently connected sources, then connects exactly one source to the tracking plan through recued-core.segment.tracking_plan.source.add. It does not edit rules, remove sources, delete tracking plans, mutate source settings, change write keys, or call arbitrary Segment routes.

Workflow origin for the Smartsheet row discussion closure loop. It reads one Smartsheet row and current row discussions for context, creates exactly one owner-provided row-level discussion through recued-core.smartsheet.row.discussion.create, and when the discussion succeeds it seeds durable data.shared closure state for smartsheet-row-discussion-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not add rows, edit cells, delete rows, share sheets, send update requests, upload attachments, mutate automations or proofs, or otherwise mutate Smartsheet beyond the owner-approved row discussion.

Workflow origin for the Todoist task comment closure loop. It reads one Todoist task and current task comments for context, creates exactly one owner-provided task comment through recued-core.todoist.comment.create, and when the comment succeeds it seeds durable data.shared closure state for todoist-task-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, move, close, reopen, delete, label, section, project, remind, template, webhook, or otherwise mutate Todoist tasks.

Workflow origin for the Trello card comment closure loop. It reads one Trello card and current comment actions for context, creates exactly one owner-provided card comment through recued-core.trello.card.comment.create, and when the comment succeeds it seeds durable data.shared closure state for trello-card-comment-closure-watcher. It uses deterministic owner-provided copy rather than AI and does not create, update, archive, move, delete, attach to, assign, label, checklist, due-complete, webhook, or otherwise mutate Trello cards.

Vendor-agnostic Layer-1 silent producer wrapping the post-substrate-canary `commitment_tracker` topic per spec § A.9.2c. Subscribes to bus events from BOTH connection.api.hubspot.contact AND connection.api.salesforce.contact updates; for each fired contact reads any housekeeping-computed row via `enrichment-list` filtered to the canonical `system.housekeeping.commitment_tracker` author, then re-emits it through the recipe cycle so the row carries an up-to-date `cursor_at` reflecting the contact touch. The substrate-side AI compute path (full Pass-4 evidence-quality fold — authorship_acceptance ['user', 'crm_user', 'unknown'] + lifecycle_state_acceptance ['point_in_time', 'completed'] + body_state_acceptance ['inline_body'] + dedupe_acceptance 'exact_only' + per-contact perspective fan-in via extractContactIdentity) lands in `backend/server/src/housekeeping/engagement-aggregates/commitment-tracker.ts` paralleling the P5 sentiment + NBA producers. Recipe writes carry `authored_by_recipe_id` distinct from `system.housekeeping.commitment_tracker` so both rows coexist on the unique `(topic, scope, target_id, authored_by_recipe_id)` index without conflict. Honest empty default per spec — when no housekeeping row exists the recipe writes an empty `commitments[]` rather than synthesizing speculative commitments at the recipe layer (no AI runs at the recipe level; substrate-side housekeeping is the canonical compute path). Trust default `manual` per D-132 — user must promote at MANUAL_RUN_THRESHOLD before the substrate producer fires; pool default `free_only` per spec § P6.B. Pack-level body-content MCP grant per spec § A.9.5 ships through the `crm-commitment-tracker` pack manifest's `mcp_body_visibility_grants: ['data.contact.engagements.body_content']`.

Approval-gated completion for one Google Tasks task. It reads the target task for context, then sets status to completed with the current timestamp through the bounded recued-core.google-tasks task.status.set operation. It does not delete tasks, clear completed tasks, edit hidden state, or use arbitrary Google API passthrough.

Approval-gated Quo task completion workflow. It reads one task for context, then completes that single task through recued-core.quo.task.complete. It never deletes tasks, sends messages, mutates contacts, changes phone-number settings, creates webhooks, or calls arbitrary Quo endpoints.

Computes days since last email/call/meeting and recent interaction count for contact view.

Owner-invoked action half of the GitHub Actions to Linear exception handoff loop. It reads one awaiting_owner_approval proposal written by github-linear-ci-failure-proposal, then either creates exactly one Linear issue from deterministic GitHub context or dismisses the proposal as no Linear work needed. Running this recipe is the owner's approval or decline. It re-reads the GitHub workflow run before creating Linear work and takes no outward-facing action when there is no pending proposal, the live workflow run no longer has conclusion failure, or the required Linear destination is missing. Linear Reviews, GitHub Actions notifications, workflow logs, rerun controls, branch protection, Linear's GitHub integration, and GitHub issue syncing should own the normal path.

Tracks contract renewal status with visual alerts for approaching/overdue renewals.

Computes weighted risk subscores for activity, close date, and contacts, with optional AI narrative.

Computes weekly pipeline metrics across all open deals.

Generates price increase email draft with AI (toggle via enable_ai). Includes calculated increase %, configurable value justifications, and restored customer name.

Tracks proposal expiration status with dynamic checklist and summary.

Scheduled adopter for Confluence inline comment reply closure rows seeded by reply-confluence-inline-comment-with-closure. It lists only Recued-originated inline-comment reply watches, re-reads a bounded batch of Confluence page and that page's inline comments, and closes or flags the shared row when Confluence reports the watched root comment resolved, the comment is no longer returned, or the page reaches a configured terminal status. It can notify the owner on resolution, disappearance, or terminal page status, but it never creates, updates, resolves, deletes, or comments on Confluence content, updates pages, changes tasks, alters labels, changes permissions, creates properties, configures automations, or calls arbitrary Atlassian endpoints.

Read-only review brief for one Confluence page. It reads the storage-format page body, labels, comments, children, and versions, then summarizes the page through the AI gateway and renders review tables. It does not mutate pages, download attachments, change permissions, or call arbitrary Atlassian endpoints.

Scheduled read-only activity brief for one Confluence Space. It lists recent pages, blog posts, and open tasks through the recued-core.confluence pack, renders compact tables, and optionally sends an in-app nudge when work is visible. It never edits pages, downloads attachments, changes permissions, or calls arbitrary Atlassian endpoints.

Validates 6 critical contact data points with instant visual feedback.

Read-only Contentful operations digest. It reads one space/environment plus bounded pages of content types, entries, published entries, assets, locales, and tags, then summarizes editorial inventory, model shape, publication state, and operational follow-up. It never creates, updates, publishes, deletes, uploads assets, mutates schemas, or calls arbitrary Contentful routes.

Read-only Contentful entry brief. It reads one entry, its content type schema, and its descendants/referenced assets, then summarizes publication state, editable fields, reference footprint, and content-model context. It never creates, updates, publishes, deletes, uploads assets, mutates schemas, or calls arbitrary Contentful routes.

Transcode a source video into a compact H.264/AAC MP4 at a chosen encoder preset using the paired recued-server's local ffmpeg tool. Ticks every 2 minutes. The converted file is captured as a Gateway-gated data.file ref (the recipe never controls the output path — no arbitrary-write surface) and surfaced to the card by ref; a downstream step reads it via { file_ref }.

Approval-gated Wave estimate conversion workflow. It reads one estimate, optionally marks it accepted, converts it into one invoice, then reads the new invoice for confirmation. It does not send the invoice, record payments, delete estimates/invoices, mutate customers/products/accounts/taxes, or call arbitrary GraphQL.

Approval-gated Acuity appointment creation workflow. It reads calendars, appointment types, availability, forms, and add-ons for context, then creates one appointment through recued-core.acuity.appointment.create. It does not mutate calendars, appointment types, clients outside the appointment booking, forms, packages, certificates, webhooks, or arbitrary endpoints.

Approval-gated Apollo account creation. It searches existing accounts, users, and account stages for context, then creates one account through recued-core.apollo.account.create with an explicit name and optional domain, owner, stage, phone, and address. It does not update accounts, delete accounts, bulk-create accounts, mutate account stages, search organizations, enrich records, or call arbitrary Apollo endpoints.

Approval-gated Apollo contact creation. It searches accounts, contact stages, lists, and existing saved contacts for context, then creates one deduped contact through recued-core.apollo.contact.create. It does not update contacts, bulk-create contacts, change owner or stage in batch, enrich people, reveal unsaved email or phone data, send email, or call arbitrary Apollo endpoints.

Approval-gated Apollo deal creation. It reads the related account, users, deal stages, and existing deals for context, then creates one deal through recued-core.apollo.deal.create. It does not update deals, delete deals, bulk-create deals, mutate account or contact stages, enrich organizations, or call arbitrary Apollo endpoints.

Approval-gated Apollo task creation. It reads the target contact, users, and existing tasks for context, then creates one scheduled follow-up task through recued-core.apollo.task.create. It does not update tasks, delete tasks, complete calls, send emails, enrich contacts, or call arbitrary Apollo endpoints.

Owner-invoked action half of the Sentry to Linear exception handoff loop. It reads one awaiting_owner_approval proposal written by sentry-linear-issue-proposal, then either creates exactly one Linear issue from deterministic Sentry context or dismisses the proposal as no Linear work needed. Running this recipe is the owner's approval or decline. It re-reads the Sentry issue before creating Linear work and takes no outward-facing action when there is no pending proposal, the live Sentry issue is no longer unresolved, or the required Linear destination is missing. Native Sentry to Linear issue tracking should own the normal create/link/sync path.

Owner-invoked create half of the core mail-to-commitment loop. It reads one awaiting_owner_approval proposal written by mail-commitment-proposal-producer, optionally targeted by proposal_thread_key, creates a Recued commitment from the proposal, links the commitment back to the source mail record, and marks the proposal created. This recipe is manual-only: running it is the owner's approval to turn the proposed mail promise into durable Recued accountability.

Owner-invoked create half of the core mail-to-task loop. It reads one awaiting_owner_approval proposal written by mail-task-proposal-producer, optionally targeted by proposal_thread_key, creates a Recued task from the proposal, links the task back to the source mail record, and marks the proposal created. This recipe is manual-only: running it is the owner's approval to turn the proposed mail action into durable Recued work.

Owner-invoked action half of the Vercel to Statuspage incident loop. It reads one awaiting_owner_approval proposal written by vercel-statuspage-incident-proposal, then either creates exactly one Statuspage incident from deterministic proposal copy or dismisses the proposal as no customer impact. Running this recipe is the owner's approval or decline. It takes no outward-facing action when there is no pending proposal or required Statuspage incident copy is missing.

Approval-gated Asana task intake workflow. It reads the destination workspace for context, creates exactly one task with bounded task fields, and can add one optional initial comment through recued-core.asana. It does not update, complete, move, delete, attach files, mutate projects or sections, edit custom fields, manage dependencies, or call arbitrary Asana endpoints.

Workflow origin for the Asana task closure loop. It reads one Asana workspace and optional project for context, creates exactly one owner-approved task through recued-core.asana.task.create, and when the task succeeds it seeds durable data.shared closure state for asana-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, complete, move, delete, attach files, assign, schedule, comment on, edit custom fields, manage dependencies, add followers or tags, create projects or sections, or otherwise mutate Asana beyond the approved task create.

Approval-gated Attio company creation. It searches existing company records for context, then creates one company through recued-core.attio.company.create with explicit name and domain values plus optional description, team, and location. It does not update companies, delete companies, bulk-create companies, mutate schema, upload files, create notes, create tasks, or call arbitrary Attio endpoints.

Approval-gated Attio deal creation. It searches companies, workspace members, and existing deals for context, then creates one deal through recued-core.attio.deal.create with explicit name and optional stage, owner, value, person, and company links. It does not update deals, delete deals, bulk-create deals, mutate schema, create tasks, create notes, or call arbitrary Attio endpoints.

Approval-gated Attio task creation. It lists workspace members and existing tasks for context, then creates one plaintext follow-up task through recued-core.attio.task.create against an explicit Attio linked-record locator. It does not update tasks, delete tasks, complete tasks, update records, create notes, mutate schema, or call arbitrary Attio endpoints.

Approval-gated Attio person creation. It searches existing records and companies for context, then creates one person through recued-core.attio.person.create with an explicit email address and optional name, description, company link, and LinkedIn URL. It does not update people, delete people, bulk-create people, mutate schema, upload files, create notes, create tasks, or call arbitrary Attio endpoints.

Approval-gated BambooHR employee creation. It reads available fields for context, then creates one employee through recued-core.bamboohr.employee.create with explicit first name, last name, work email, job title, department, location, hire date, and employee number. It does not update employees, write table rows, upload photos or files, create dependents, mutate benefits/payroll, assign policies, or call arbitrary BambooHR endpoints.

Approval-gated Bitbucket Cloud issue creation workflow. It reads the authenticated user and target repository for context, then creates exactly one issue with bounded title, Markdown body, kind, and priority through recued-core.bitbucket. It does not update or delete existing issues, change assignees, upload attachments, change repository settings, run pipelines, create webhooks, or call arbitrary Bitbucket APIs.

Approval-gated Buffer idea intake workflow. It reads the organization and idea groups for context, then creates exactly one content idea with title, body, target services, optional planning date, tags, media, and group placement through recued-core.buffer. It does not create posts, publish, edit or delete existing ideas, reorder queues, mutate channels, or call arbitrary GraphQL.

Approval-gated Buffer post creation workflow. It reads the destination channel for context, then creates exactly one post with caller-supplied text, schedule mode, scheduled time, tags, optional documented assets, and optional channel metadata through recued-core.buffer. It does not edit existing posts, delete posts, reorder queues, mutate channels, manage team settings, upload local files, or call arbitrary GraphQL.

Approval-gated Canva design creation workflow. It reads profile and capabilities for context, then creates one preset or custom Canva design through recued-core.canva.design.create. It does not copy existing designs, create from brand templates, import files, upload assets, export content, mutate folders, or call arbitrary Canva endpoints.

Approval-gated Chargebee Product Catalog 2.0 item and item-price creation workflow. It checks existing item and price IDs, then creates one item and one item price using Chargebee's documented form-encoded bodies. It does not update, archive, delete, attach, bulk mutate, create coupons, create subscriptions, or call arbitrary Chargebee endpoints.

Approval-gated Chargebee customer creation workflow. It searches for an existing customer ID, then creates one customer through recued-core.chargebee.customer.create using Chargebee's documented form-encoded customer body shape. It does not update customers, delete customers, mutate payment sources, create subscriptions, create invoices, or call arbitrary Chargebee endpoints.

Approval-gated Chargebee hosted checkout creation workflow. It reads customer and item-price context, then creates one hosted checkout page through recued-core.chargebee.hosted_page.checkout.create using Chargebee's documented checkout_new_for_items form-encoded body. It does not directly create subscriptions, update subscriptions, manage payment sources, collect invoices, acknowledge hosted pages, or call arbitrary Chargebee endpoints.

Approval-gated quick intake for one ClickUp List. It reads the destination list for context, creates exactly one task with bounded task fields, and can add one optional initial comment through recued-core.clickup. It does not expose user invites, ACL edits, uploads, bulk imports, deletes, or arbitrary ClickUp endpoints.

Workflow origin for the ClickUp task closure loop. It reads one ClickUp List for context, creates exactly one owner-approved task through recued-core.clickup.task.create, and when the task succeeds it seeds durable data.shared closure state for clickup-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, transition, close, delete, attach to, assign, tag, checklist, time-track, link, webhook, comment on, or otherwise mutate ClickUp beyond the approved task create.

Approval-gated Close lead intake workflow. It reads current lead statuses, creates one lead with one nested contact, and returns the created record. It never deletes or merges leads, creates tasks or opportunities implicitly, sends email/SMS/calls, mutates custom fields, uploads files, or calls arbitrary Close routes.

Approval-gated Close pipeline workflow. It reads available pipelines and opportunity statuses, creates one opportunity on one lead, and creates one lead follow-up task. It never sends outbound communication, changes statuses in bulk, deletes records, uploads files, creates call tasks, or calls arbitrary Close routes.

Approval-gated Coda page intake workflow for one doc. It reads destination doc metadata and existing pages, creates exactly one page by name through recued-core.coda, and reads Coda mutation status once. It never updates existing pages, deletes pages, shares docs, publishes docs, exports content, or calls arbitrary Coda APIs.

Approval-gated Coda row intake workflow for one table. It reads the destination table and visible columns, inserts or upserts exactly one row from provided cell edits through recued-core.coda, and reads Coda mutation status once. It never deletes rows, writes to views intentionally, shares docs, publishes docs, exports content, or calls arbitrary Coda APIs.

Approval-gated Cohere workflow for creating one async embed job from an existing dataset. It reads the input dataset and recent embed jobs first, then calls recued-core.cohere.embed_job.create with an explicit model, dataset ID, input type, optional name, embedding types, and truncate policy. It does not upload or delete datasets, cancel unrelated jobs, call streaming chat/generate endpoints, use connectors, mutate fine-tuned models, or call arbitrary Cohere routes.

Approval-gated page creation for one Confluence Space. It creates exactly one page from storage-format body content through recued-core.confluence.page.create, optionally under a parent page. It does not upload files, alter permissions, purge/delete content, or use arbitrary Atlassian endpoints.

Approval-gated Contentful draft creation workflow. It reads the target content type schema, creates exactly one draft entry from a caller-supplied locale-wrapped fields object, and returns the new entry for review. It does not publish, update existing entries, delete, upload/process assets, mutate content types, or call arbitrary Contentful routes.

Creates a HubSpot deal via the `recued-core.hubspot.deal.create` Tier-P op-step. `deal.create` is WRITE-tier, so the call routes through the gateway's preflight approval: the run pauses (awaiting_approval), surfaces a `notification.ask` ('Approve creating this deal?'), and only after you approve does it POST the deal — emitting a `connection.gateway` audit row. Prerequisite: the HubSpot deals write grant must be in place; write ops are NOT auto-granted at enrollment (read-tier only, Invariant 3), so grant it explicitly first.

Approval-gated Fly.io app creation workflow. It reads current token metadata, platform regions, and existing apps for context, validates the caller-supplied app name and organization slug, then creates exactly one app through recued-core.flyio.app.create. It does not create machines or volumes, delete apps, mint deploy tokens, mutate secrets, assign IPs, or call arbitrary Fly.io API routes.

Approval-gated Maxio customer creation workflow. It searches for possible existing customers, creates exactly one customer from a caller-supplied customer object through recued-core.maxio, and returns the created record. It does not create subscriptions, payment profiles, invoices, usage, allocations, refunds, deletes, or arbitrary Maxio calls.

Approval-gated Fly.io volume creation workflow. It reads the target app, existing volumes, and platform regions for context, validates the caller-supplied name, region, and size, then creates exactly one volume through recued-core.flyio.volume.create. It does not create machines, attach or delete volumes, extend existing volumes, mutate secrets, or call arbitrary Fly.io API routes.

Approval-gated Freshdesk ticket intake workflow. It reads agent, group, ticket-field, and solution context, then creates exactly one ticket with caller-supplied subject, requester email, description, status, priority, source, type, and tags through recued-core.freshdesk. It does not update existing tickets, reply, delete, bulk update, attach files, mutate contacts or companies, change automations/admin settings, or call arbitrary Freshdesk endpoints.

Approval-gated GitHub issue creation workflow. It reads the authenticated user and target repository for context, then creates exactly one issue with bounded title, body, labels, assignees, and milestone fields through recued-core.github-pack. It does not update existing issues, post comments, create or update pull requests, merge code, rerun or cancel workflows, dispatch workflows, mutate branches, change repository settings, touch secrets or collaborators, create webhooks, or call arbitrary GitHub APIs.

Workflow origin for the GitHub issue closure loop. It reads the target repository for context, creates exactly one owner-approved issue through recued-core.github-pack.issue.create, and when the issue succeeds it seeds durable data.shared closure state for github-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, close, reopen, delete, transfer, label, assign, lock, comment on, create pull requests for, or otherwise mutate GitHub issues beyond the approved issue create.

Approval-gated GitLab.com issue creation workflow. It reads the authenticated user and target project for context, then creates exactly one issue with bounded title, description, labels, assignee IDs, due date, and confidentiality fields through recued-core.gitlab. It does not update existing issues, post notes, create or update merge requests, merge or approve code, trigger or cancel pipelines, mutate branches or tags, change project settings, touch runners or admin APIs, create webhooks, or call arbitrary GitLab APIs.

Approval-gated focus-block creation workflow. It reads the target calendar and free/busy state for context, then creates exactly one opaque Google Calendar event through recued-core.google-calendar when title, start, and end are present. It does not edit existing events, delete events, mutate ACLs, create calendars, create conferences, import events, or call arbitrary Google Calendar APIs.

Approval-gated meeting-notes workflow. It creates one blank Google Docs document by title, then inserts a fixed meeting-notes scaffold through recued-core.google-docs.document.text.insert. It does not search Drive, share files, export documents, mutate styles/images/tables, delete content, or call arbitrary Google APIs.

Approval-gated Google Meet link creation workflow. It creates one Meet space with explicit access, entry-point, moderation, attendance, recording, transcription, and smart-notes settings through recued-core.google-meet.space.create. It does not schedule a Calendar event, invite attendees, patch space settings after creation, start live media capture, download artifacts, or call arbitrary Google APIs.

Approval-gated status-deck workflow. It creates one blank Google Slides presentation by title, then inserts a fixed three-slide status update scaffold through recued-core.google-slides.presentation.slide.create. It does not search Drive, share files, export presentations, insert images/charts/tables/videos, delete slides, mutate speaker notes, or call arbitrary Google APIs.

Approval-gated Mailchimp campaign draft workflow. It reads the destination audience for context, creates exactly one regular campaign draft, and can update that draft with HTML/plain-text content. It never sends, schedules, cancels, pauses, resumes, deletes, uploads files, mutates automations, or calls arbitrary Mailchimp endpoints.

Workflow origin for the Google Tasks task closure loop. It reads one task list for context, creates exactly one owner-approved active Google Task through recued-core.google-tasks.task.create, and when the task succeeds it seeds durable data.shared closure state for google-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not complete, update, delete, move, reorder, rename lists, mutate links, touch hidden/deleted or assignment-source fields, clear completed tasks, or otherwise mutate Google Tasks beyond the approved task create.

Approval-gated Greenhouse candidate creation. It optionally reads target jobs for context, then creates one candidate profile through recued-core.greenhouse.candidate.create with explicit name, contact, tags, and optional nested application payload. It does not update existing candidates, merge, anonymize, delete, move applications, hire/reject applicants, create offers, upload attachments, or call arbitrary Greenhouse endpoints.

Approval-gated Help Scout conversation intake workflow. It reads inbox and folder context, then creates exactly one conversation with a caller-supplied subject, customer email, initial thread text, status, type, and tags through recued-core.helpscout. It does not update existing conversations, reply to existing conversations, mutate customers or users, upload or download attachments, delete, bulk-mutates, run workflows, change inbox/admin settings, or call arbitrary Help Scout endpoints.

Approval-gated Heroku app creation workflow. It reads current account, regions, stacks, and existing apps for context, then creates exactly one app through recued-core.heroku.app.create. It does not create dynos, builds, domains, config vars, add-ons, pipelines, teams, spaces, log sessions, or arbitrary Heroku API calls.

Approval-gated Heroku build creation workflow. It reads the app and recent builds, then creates exactly one build from a caller-supplied gzipped source blob URL through recued-core.heroku.build.create. It does not upload files itself, create apps, mutate config vars, roll back releases, stop or restart dynos, delete resources, or call arbitrary Heroku API routes.

Approval-gated Heroku domain creation workflow. It reads the app and existing domains, then creates exactly one custom domain through recued-core.heroku.domain.create using the documented hostname and sni_endpoint body fields. It does not enable or disable ACM, mutate SNI endpoints, delete domains, create log drains, change DNS, mutate config vars, or call arbitrary Heroku API routes.

Approval-gated Hugging Face workflow for creating one collection. It searches existing collections first, then calls recued-core.huggingface.collection.create with an explicit title, namespace, optional description, optional initial item, and privacy flag. It does not patch or delete collections, mutate collection items after creation, create repositories, download files, mutate settings, or call arbitrary Hugging Face routes.

Approval-gated Hugging Face workflow for creating one repository discussion or pull request discussion. It reads existing discussions first, then calls recued-core.huggingface.discussion.create with an explicit repository type, namespace, repository, title, and description. It does not comment, merge, pin, change status, create commits, create repositories, mutate settings, or call arbitrary Hugging Face routes.

Approval-gated incident.io action creation workflow. It reads the target incident, existing actions, and users for context, then creates exactly one action through recued-core.incidentio.action.create with caller-supplied description and optional assignee. It does not edit incidents, update or delete existing actions, create follow-ups, mutate schedules, escalations, status pages, settings, API keys, or call arbitrary incident.io APIs.

Approval-gated incident.io follow-up creation workflow. It reads the target incident, existing follow-ups, teams, and users for context, then creates exactly one follow-up through recued-core.incidentio.follow_up.create with caller-supplied title, description, assignee, team, priority, category, external reference, and labels. It does not edit incidents, update or delete existing follow-ups, create actions, mutate schedules, escalations, status pages, settings, API keys, or call arbitrary incident.io APIs.

Approval-gated incident.io incident creation workflow. It reads identity, severities, incident statuses, users, teams, and recent incidents for context, then creates exactly one incident through recued-core.incidentio.incident.create with caller-supplied idempotency key, visibility, name, summary, severity ID, status ID, incident type ID, mode, and optional custom fields. It does not edit existing incidents, create actions or follow-ups, mutate schedules, escalations, status pages, settings, API keys, or call arbitrary incident.io APIs.

Approval-gated quick intake for one Jira project. It searches the destination project for context, creates exactly one issue with a bounded Jira fields object, and can add one optional initial comment through recued-core.jira. It does not delete, bulk mutate, attach files, notify watchers, mutate project settings, or call arbitrary Jira endpoints.

Workflow origin for the Jira issue closure loop. It creates exactly one owner-approved issue through recued-core.jira.issue.create, and when the issue succeeds it seeds durable data.shared closure state for jira-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, transition, assign, delete, comment on, attach to, link, watch, vote on, add worklogs to, or otherwise mutate Jira issues beyond the approved issue create.

Approval-gated Jotform report creation workflow. It reads one form and existing reports for context, then creates one report through recued-core.jotform.report.create using Jotform's documented form-encoded title, list_type, and fields body shape. It does not delete reports, mutate submissions, download files, create webhooks, mutate labels, or call arbitrary endpoints.

Approval-gated Jotform form creation workflow. It reads the current account for context, then creates one form through recued-core.jotform.form.create using Jotform's documented form-encoded questions[*], properties[*], and emails[*] body shape. It does not clone forms, mutate folders, mutate labels, create webhooks, change user settings, delete anything, download files, or call arbitrary Jotform endpoints.

Approval-gated Klarna order placement workflow. It creates exactly one order from one successful Klarna authorization token and documented cart payload through recued-core.klarna.order.create. It does not capture, refund, cancel, update, create customer tokens, or call arbitrary endpoints.

Approval-gated Klarna payment-session creator. It opens one Klarna Payments API session with cart details, returns session_id, client_token, and available payment methods, and does not place an order, capture funds, cancel authorizations, generate customer tokens, or call arbitrary endpoints.

Approval-gated Lever opportunity creation. It optionally reads target postings, stages, users, sources, and tags for context, then creates one opportunity through recued-core.lever.opportunity.create with explicit name, contact, posting, source, tag, stage, and owner data. It does not upload resumes, update existing opportunities, move stages, archive, create panels or interviews, mutate postings or requisitions, or call arbitrary Lever endpoints.

Approval-gated Linear issue intake workflow. It reads team, workflow-state, and project lists for context, creates exactly one issue with bounded Linear fields, and can add one optional initial comment through recued-core.linear. It does not update existing issues, move status after creation, delete, archive, label, subscribe, mutate projects, manage webhooks, or call arbitrary Linear GraphQL.

Workflow origin for the Linear issue closure loop. It creates exactly one owner-approved issue through recued-core.linear.issue.create, and when the issue succeeds it seeds durable data.shared closure state for linear-issue-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, move, cancel, complete, delete, archive, assign, label, subscribe to, comment on, or otherwise mutate Linear issues beyond the approved issue create.

Approval-gated Maxio invoice creation workflow. It reads the subscription and recent invoices, creates exactly one invoice from a caller-supplied invoice object through recued-core.maxio, then re-lists invoices for confirmation. It does not issue, send, void, reopen, refund, record payments, create payment profiles, delete resources, or call arbitrary Maxio endpoints.

Approval-gated Maxio subscription creation workflow. It previews a subscription signup and then creates exactly one subscription from the same caller-supplied subscription object through recued-core.maxio. It does not create or update payment profiles, record usage, allocate components, create invoices, alter coupons, refund, void, delete, or call arbitrary Maxio endpoints.

Approval-gated task intake for one Microsoft To Do task list. It creates exactly one task through recued-core.microsoft-todo, then can add checklist items and one linked source resource. It does not delete, complete, batch-update, mutate Outlook categories, attach files, touch open extensions, or call arbitrary Graph endpoints.

Workflow origin for the Microsoft To Do task closure loop. It reads one task list for context, creates exactly one owner-approved active To Do task through recued-core.microsoft-todo.task.create, and when the task succeeds it seeds durable data.shared closure state for microsoft-todo-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, complete, delete, batch-update, mutate checklist items, add linked resources, touch attachments or open extensions, mutate Outlook categories outside task creation, or otherwise mutate Microsoft To Do beyond the approved task create.

Approval-gated Mollie customer intake. It reads nearby customers, then creates exactly one customer profile with caller-supplied name, email, and locale through recued-core.mollie. It does not create payment methods, mandates, subscriptions, checkout payments, refunds, webhooks, or arbitrary Mollie endpoints.

Approval-gated Mollie checkout creator. Reads available methods, then creates exactly one payment with amount, currency, description, and redirect URL through recued-core.mollie. Excludes refunds, captures, cancels, mandates, subscriptions, webhooks, and arbitrary endpoints.

Approval-gated monday.com item intake workflow. It reads the destination board and groups for context, creates exactly one item with bounded board, group, name, and column-values fields, and can add one optional initial update through recued-core.monday. It does not update existing items, move or archive items, create groups, mutate columns/schema, delete, upload files, invite users, send notifications, or call arbitrary monday.com GraphQL.

Approval-gated Neon preview branch workflow for one project. It reads the project and current branch list for context, then calls recued-core.neon.branch.create with one branch name, optional parent branch, and initialization mode. It does not create endpoints, set expirations, alter protected branches, restore/reset/delete branches, retrieve connection URIs, reveal passwords, or call arbitrary Neon APIs.

Approval-gated Notion page intake workflow for one data source. It reads the destination data-source schema, searches for similarly titled pages for context, creates exactly one page with a conventional Name title property and optional paragraph body, and can add one optional initial comment through recued-core.notion. It does not update existing pages, append blocks after creation, edit comments, update to-do blocks, delete, export, move pages, alter permissions, or call arbitrary Notion APIs.

Approval-gated OneSignal message creation workflow. It reads recent notification context, then creates exactly one push, email, or SMS notification through recued-core.onesignal.notification.create using explicit app, audience, and message fields. It never creates segments, mutates users or subscriptions, cancels existing notifications, exports history, deletes records, or calls arbitrary OneSignal APIs.

Approval-gated OneSignal segment creation workflow. It creates exactly one segment through recued-core.onesignal.segment.create using documented filter expressions. It never sends notifications, deletes segments, mutates users or subscriptions, exports reports, or calls arbitrary OneSignal APIs.

Approval-gated Outreach account creation. It reads existing accounts for context, then creates one account through recued-core.outreach.account.create with an explicit name. It does not update accounts, delete accounts, import accounts, write to-many relationships, create prospects, enroll sequences, or call arbitrary Outreach endpoints.

Approval-gated Outreach prospect creation. It reads accounts and users for context, then creates one prospect through recued-core.outreach.prospect.create with explicit email, name, title, and optional account relationship. It does not update prospects, delete prospects, enroll sequences, import prospects, write calls, send mail, or call arbitrary Outreach endpoints.

Approval-gated Outreach snippet creation. It reads existing snippets for context, then creates one snippet through recued-core.outreach.snippet.create with an explicit name and HTML body. It does not update snippets, delete snippets, associate snippets with sequence steps, create sequence steps, send mail, or call arbitrary Outreach endpoints.

Approval-gated Outreach template creation. It reads existing templates for context, then creates one template through recued-core.outreach.template.create with an explicit subject and HTML body. It does not update templates, delete templates, associate sequence templates, create sequence steps, send mail, or call arbitrary Outreach endpoints.

Approval-gated PandaDoc document creation workflow. It reads one template for context, then creates one document from that template through recued-core.pandadoc.document.create_from_template using supplied recipients, tokens, fields, metadata, and tags. It does not upload files, create templates, send the document, download files, create embedded sessions, mutate folders, delete, or call arbitrary PandaDoc endpoints.

Workflow origin for the Microsoft Planner task closure loop. It reads one Planner plan and optional bucket for context, creates exactly one owner-approved Planner task through recued-core.planner.task.create, and when the task succeeds it seeds durable data.shared closure state for planner-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, complete, delete, reorder, relabel plans, mutate buckets, alter board formats, change group membership, touch premium Planner resources, or otherwise mutate Planner beyond the approved task create.

Approval-gated Quo contact intake workflow. It reads contact custom field definitions for context, then creates one contact through recued-core.quo.contact.create with documented defaultFields and source metadata. It does not delete contacts, mutate phone settings, send messages, create tasks, create webhooks, or call arbitrary Quo endpoints.

Approval-gated Quo follow-up task workflow. It reads recent conversation context for one phone number, then creates one task linked to one conversation through recued-core.quo.task.create_for_conversation. It does not send messages, delete tasks, change due dates after creation, mutate contacts, create webhooks, or call arbitrary Quo endpoints.

Approval-gated Railway custom domain workflow. It reads the target service context, creates exactly one custom domain through recued-core.railway, then lists service domains for DNS review. It does not delete domains, mutate variables, deploy services, change ports beyond the requested target port, or call arbitrary Railway GraphQL.

Approval-gated Railway project creation workflow. It creates exactly one project from a caller-supplied ProjectCreateInput object through recued-core.railway, then returns the created project for review. It does not create services, deploy code, mutate variables, create domains or volumes, delete resources, or call arbitrary Railway GraphQL.

Approval-gated Railway volume backup workflow. It reads one volume instance, creates exactly one backup through recued-core.railway, then lists backups for confirmation. It does not restore backups, delete backups, delete volumes, mutate services, deploy code, mutate variables, or call arbitrary Railway GraphQL.

Approval-gated Recurly account creation. It searches existing accounts for context, then creates one account through recued-core.recurly.account.create with an explicit account code and optional email, name, and company. It does not add billing information, update accounts, deactivate accounts, redact accounts, create subscriptions, create transactions, or call arbitrary Recurly endpoints.

Approval-gated Recurly coupon creation. It searches existing coupons and plans for context, then creates one coupon through recued-core.recurly.coupon.create with explicit code, name, discount type, and optional percent or currency discounts. It does not update coupons, expire coupons, create unique codes, mutate redemptions, mutate subscriptions, or call arbitrary Recurly endpoints.

Approval-gated Recurly item creation. It searches existing items and plans for context, then creates one item through recued-core.recurly.item.create with explicit code, name, and revenue schedule type. It does not update items, deactivate items, create plans, create add-ons, mutate subscriptions, or call arbitrary Recurly endpoints.

Approval-gated Recurly plan creation. It searches existing plans, items, and business entities for context, then creates one plan through recued-core.recurly.plan.create with explicit code, name, and currency pricing payload. It does not update plans, remove plans, create subscriptions, mutate add-ons, mutate coupons, or call arbitrary Recurly endpoints.

Approval-gated Recurly subscription creation. It reads account, plan, subscription, and coupon context, previews the purchase payload through recued-core.recurly.purchase.preview, then creates one subscription through recued-core.recurly.subscription.create. It does not create purchases, update subscriptions, cancel subscriptions, terminate subscriptions, mutate billing information, collect invoices, create transactions, or call arbitrary Recurly endpoints.

Approval-gated Rootly incident action-item creation workflow. It reads the target incident, existing action items, and users for context, validates the caller-supplied summary, then creates exactly one incident action item through recued-core.rootly.action_item.incident.create with Rootly JSON:API fields for summary, description, assignee user, assignee teams, priority, status, and due date. It does not edit incidents, update or delete existing action items, mutate alerts, schedules, escalation policies, services, teams, users, API keys, or arbitrary Rootly API routes.

Approval-gated Rootly incident creation workflow. It reads the current user, severities, services, teams, and recent incidents for context, validates the caller-supplied title, then creates exactly one incident through recued-core.rootly.incident.create using Rootly JSON:API fields for title, summary, kind, privacy, severity, services, teams, labels, and status. It does not edit existing incidents, create action items, mutate alerts, schedules, escalation policies, services, teams, severities, statuses, users, API keys, or arbitrary Rootly API routes.

Approval-gated Salesloft task creation. It reads the target person and existing tasks for context, then creates one follow-up task through recued-core.salesloft.task.create with explicit subject, person, account, assignee, due date, task type, and description fields. It does not update tasks, delete tasks, bulk-reschedule tasks, bulk-cancel tasks, send emails, complete calls, or call arbitrary Salesloft endpoints.

Approval-gated Salesloft person creation. It reads accounts, users, and person stages for context, then creates one person through recued-core.salesloft.person.create with explicit name, email, phone, title, account, owner, LinkedIn URL, and person stage fields. It does not update people, delete people, create accounts, upsert people, soft-delete records, import data, or call arbitrary Salesloft endpoints.

Approval-gated Segment tracking-plan creation workflow. It reads existing tracking plans for context, then creates exactly one tracking plan with caller-supplied name, type, and optional description through recued-core.segment.tracking_plan.create. It does not attach sources, add rules, delete plans, mutate IAM, change write keys, or call arbitrary Segment routes.

Approval-gated ServiceNow change request workflow. It creates one change request through recued-core.servicenow.change.create with typed planning fields, optionally linked to an incident or CI. It does not mutate CAB approvals, execute workflows, delete records, mutate CMDB records, upload attachments, or call arbitrary ServiceNow APIs.

Approval-gated ServiceNow incident intake workflow. It creates one incident through recued-core.servicenow.incident.create with typed fields, then summarizes the created record. It does not delete records, order catalog items, upload attachments, import data, mutate CMDB records, or call arbitrary ServiceNow APIs.

Approval-gated Shippo rate-shopping workflow. It creates one shipment from explicit sender address, recipient address, and parcel objects through recued-core.shippo.shipment.create, then renders returned rates. It does not purchase labels, create refunds, mutate orders, manage carrier accounts, schedule pickups, create manifests, or call arbitrary Shippo endpoints.

Approval-gated Squarespace contact workflow. It searches for likely existing contacts, creates one contact with primary email, and can optionally add one shipping address through recued-core.squarespace. It does not delete contacts, bulk import, mutate products/orders/payments, or call arbitrary endpoints.

Approval-gated Statuspage incident creation for one page. It reads the page and components for context, then creates exactly one incident through recued-core.statuspage.incident.create with caller-supplied name, status, impact, message, component IDs, and notification flags. It does not update components outside the incident payload, mutate subscribers, edit page configuration, schedule maintenance, create postmortems, delete records, or call arbitrary Statuspage APIs.

Approval-gated SurveyMonkey invite message workflow. It reads one collector for context, then creates one collector message from caller-provided JSON through recued-core.surveymonkey.message.create. It does not add recipients, send or schedule the message, delete messages, bulk import contacts, or call arbitrary SurveyMonkey endpoints.

Approval-gated SurveyMonkey web collector workflow. It reads one survey for context, then creates one weblink collector through recued-core.surveymonkey.collector.create. It does not create popup collectors, SMS/email collectors, update questions, delete collectors, create webhooks, or call arbitrary SurveyMonkey endpoints.

Approval-gated Todoist task intake workflow. It reads project, section, and label lists for context, creates exactly one task with bounded Todoist fields, and can add one optional initial comment through recued-core.todoist. It does not update existing tasks, move tasks, close/reopen tasks, delete, mutate projects/sections/labels, create reminders, upload files, or call arbitrary Todoist APIs.

Workflow origin for the Todoist task closure loop. It reads an optional Todoist project for context, creates exactly one owner-approved task through recued-core.todoist.task.create, and when the task succeeds it seeds durable data.shared closure state for todoist-task-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, move, close, reopen, delete, comment on, label, section, remind, template, webhook, or otherwise mutate Todoist beyond the approved task create.

Approval-gated Railway volume restore workflow. It reads one volume instance and its backups, then restores exactly one selected backup through recued-core.railway. It does not create backups, delete backups, delete volumes, mutate services, deploy code, mutate variables, or call arbitrary Railway GraphQL.

Approval-gated quick intake for one Trello list. It reads the destination list for context, creates exactly one card with bounded card fields, and can add one optional initial comment through recued-core.trello. It does not archive, delete, upload files, mutate webhooks, edit labels, remove members, or call arbitrary Trello endpoints.

Workflow origin for the Trello card closure loop. It reads one Trello List for context, creates exactly one owner-approved card through recued-core.trello.card.create, and when the card succeeds it seeds durable data.shared closure state for trello-card-closure-watcher. It uses deterministic owner-provided fields rather than AI and does not update, archive, move, delete, comment on, attach to, assign, label, checklist, due-complete, webhook, or otherwise mutate Trello cards beyond the approved card create.

Approval-gated Vercel environment-variable creation workflow. It reads existing environment-variable metadata with decrypt=false, then creates exactly one project environment variable through recued-core.vercel.project.env.create. It never reads secret values, updates or removes existing variables, creates deployments, mutates domains, pauses projects, deletes records, or calls arbitrary Vercel APIs.

Approval-gated Wave customer intake workflow. It reads the target business and optional existing email matches, then creates exactly one customer through recued-core.wave. It does not delete/archive customers, create invoices, record payments, mutate accounts or taxes, or call arbitrary GraphQL.

Approval-gated Wave estimate draft workflow. It reads the target business and customer, then creates exactly one estimate with caller-supplied line items through recued-core.wave. It does not send the estimate, convert it to an invoice, record deposits, delete estimates, mutate customers/products/accounts/taxes, or call arbitrary GraphQL.

Approval-gated Wave invoice draft workflow. It reads the target business and customer, then creates exactly one invoice with caller-supplied line items through recued-core.wave. It does not send the invoice, record payments, delete invoices, mutate customers/products/accounts/taxes, or call arbitrary GraphQL.

Approval-gated Wave product/service intake workflow. It reads the target business and active sales taxes, then creates exactly one product/service through recued-core.wave. It does not archive products, mutate accounts or taxes, create invoices, record payments, or call arbitrary GraphQL.

Approval-gated WooCommerce coupon workflow. It searches for an existing coupon code for context, then creates exactly one coupon with bounded offer fields through recued-core.woocommerce. It never deletes coupons, creates refunds, updates orders, mutates products, changes payment/shipping settings, edits webhooks, or calls arbitrary WordPress admin endpoints.

Approval-gated WordPress draft creation. It searches for existing posts with the same slug for context, then creates exactly one post through recued-core.wordpress with bounded editorial fields and a default draft status. It never publishes without explicit status input, deletes content, uploads media, mutates users, changes settings, installs plugins, or calls arbitrary WordPress endpoints.

Approval-gated WorkOS organization intake workflow. It searches for similarly named organizations, creates exactly one organization through recued-core.workos, and returns the created tenant record. It never deletes organizations, creates users, mutates memberships, authenticates users, exchanges tokens, exports audit logs, or calls arbitrary WorkOS APIs.

Scheduled read-only triage digest for Datadog monitor and signal health. It validates the connection, searches triggered monitors and monitor groups, reads recent logs and events through recued-core.datadog, renders compact tables, and optionally sends an in-app nudge when active signals are visible. It never creates or updates monitors, mutes monitors, changes downtimes, writes logs or events, changes dashboards, or calls arbitrary Datadog APIs.

Approval-gated YouTube playlist creation workflow. It reads the target channel for context, creates exactly one playlist with bounded title, description, privacy, and default language fields, and can optionally add one seed video through recued-core.youtube. It does not update or delete playlists, reorder or remove playlist items, upload/update/delete/rate/report videos, write comments, moderate comments, touch caption media, live controls, channel branding, subscriptions, partner administration, arbitrary Google APIs, or arbitrary YouTube passthrough.

Approval-gated Zoho CRM appointment booking workflow. It reads the selected service, then creates one scheduled appointment for a customer record and assigned service member through recued-core.zoho-crm-work. It does not delete appointments, change appointment preferences, write rescheduled-history records directly, create services, change service members, alter pricing, upload attachments, or call arbitrary Zoho endpoints.

Approval-gated Zoho CRM support case intake workflow. It reads active users for owner context, then creates exactly one Cases record through recued-core.zoho-crm-work using bounded daily support fields. It does not delete cases, close or merge tickets, mutate users/settings, bulk-import support data, upload attachments, update unrelated records, or call arbitrary Zoho endpoints.

Approval-gated Zoho CRM lead intake workflow. It reads active users for owner context, then creates exactly one lead through recued-core.zoho-crm-sales using bounded daily lead fields. It does not convert leads, create deals, create contacts/accounts, update existing records, run assignment rules, mutate settings, bulk-import, attach files, or call arbitrary Zoho endpoints.

Approval-gated Zoom meeting creation workflow. It reads the target Zoom user and user meeting settings for context, then creates exactly one scheduled Zoom meeting with bounded topic, timing, agenda, password, waiting-room, mute-on-entry, registration, approval, and auto-recording fields through recued-core.zoom. It does not update or cancel existing meetings, add registrants, change registrant status, mutate polls, delete recordings, download recording bytes, change settings, control meetings, create webhooks, or call arbitrary Zoom APIs.

Approval-gated Zuora account intake. Reads catalog context, then creates exactly one account with bill-to contact fields through recued-core.zuora. Excludes payment methods, subscriptions, invoices, orders, bill runs, webhooks, and arbitrary endpoints.

Approval-gated CRM maintenance write. Update one selected contact's phone number through the canonical contact.update operation after reviewing the read-only maintenance preview. The bound HubSpot or Salesforce contact capability pack owns the write grant, preflight approval, vendor body mapping, and audit row.

Read-only maintenance queue for contacts missing a phone number. The search runs server-side through the canonical contact.search operation, then shows the owner a short list with record ids so one selected contact can be updated through the paired approval-gated apply recipe.

Read-only investigation brief for one Datadog monitor. It reads the monitor, related monitor groups, logs, events, and optional metric timeseries through recued-core.datadog, then asks the AI summarizer for likely context, recent signal shape, missing evidence, and next investigation steps. It never mutes, updates, deletes, creates, ingests, or otherwise mutates Datadog records.

Approval-gated dbt Cloud run cancellation workflow. It reads the selected run and visible run steps for context, then cancels exactly one run through recued-core.dbt-cloud.run.cancel. It does not trigger jobs, retry or rerun failed runs, mutate jobs or projects, cancel any other run, or call arbitrary dbt API routes.

Read-only dbt Cloud workflow for reviewing one run and one documented run artifact such as run_results.json, manifest.json, or catalog.json. It does not trigger jobs, cancel runs, retry runs, mutate dbt Cloud resources, read service tokens or credentials, or call arbitrary dbt API routes.

Read-only dbt Cloud workflow for reviewing recent account jobs and runs, including job recency, run status, failures, artifacts, and operational follow-up. It does not trigger jobs, cancel runs, mutate projects/environments/jobs, read credentials or service tokens, call Discovery or Semantic Layer APIs, or use arbitrary dbt API routes.

Approval-gated dbt Cloud job trigger workflow. It reads the selected job for context, then enqueues exactly one run using that job's configured defaults and an explicit cause. It does not create or update jobs, override steps by default, retry/rerun failed runs, cancel runs, mutate projects/environments, or call arbitrary dbt API routes.

Approval-gated WorkOS offboarding workflow for one organization membership. It reads the current membership, deactivates exactly that membership through recued-core.workos, and returns the post-change membership record. It never deletes the membership or user, revokes sessions, mutates roles, authenticates users, exchanges tokens, exports audit logs, or calls arbitrary WorkOS APIs.

Generates AI-powered handoff brief when deal ownership changes. Summarizes history, key contacts, highlights, open objections, and next steps with PII protection. Activities bind to your HubSpot connection via the canonical engagement.list op.

Reactive AI producer. Listens to connection.api.hubspot.deal {created,updated} bus events; for each fired deal fetches the current record via the HubSpot connection adapter, AI-scores it 0-100 across stage progression / amount fit / deal age / engagement freshness, and upserts the `deal_health_score` enrichment per spec § A.6 cross-vendor topic. AI-classify routing follows the topic's per-pair trust state (D-132): default `manual` until promoted via Settings → Server → Housekeeping. Salesforce-flavored producer ships in D-130 against the same topic.

Reactive AI producer. Listens to connection.api.salesforce.opportunity {created,updated} bus events; for each fired opportunity fetches the current record via the Salesforce connection adapter, AI-scores it 0-100 across stage progression / amount fit / deal age / engagement freshness, and upserts the cross-vendor `deal_health_score` enrichment per spec § A.6 (D-130 P6 widening). Salesforce parallel of `deal-health-score-hubspot`; both share `variant_group: deal-health-score`. AI-classify routing follows the topic's per-pair trust state (D-132): default `manual` until promoted via Settings → Server → Housekeeping.

Reactive silent producer. Listens to connection.api.hubspot.deal {created,updated} bus events emitted by the D-129 reconciler / webhook funnel; for each fired deal fetches the current record via the HubSpot connection adapter, classifies velocity by deal age (accelerating < 14d / stable 14-30d / stalling > 30d), and upserts the `deal_velocity_signal` enrichment per spec § A.6 cross-vendor topic. Salesforce-flavored producer ships in D-130 against the same topic. Deterministic — no AI tokens.

Reactive silent producer. Listens to connection.api.salesforce.opportunity {created,updated} bus events emitted by the D-130 reconciler / CometD funnel; for each fired opportunity fetches the current record via the Salesforce connection adapter, classifies velocity by deal age (accelerating < 14d / stable 14-30d / stalling > 30d), and upserts the cross-vendor `deal_velocity_signal` enrichment per spec § A.6 (D-130 P6 widening). Salesforce parallel of `deal-velocity-signal-hubspot`; both recipes share `variant_group: deal-velocity-signal` so the marketplace card collapses across vendors. Deterministic — no AI tokens.

Extracts policy details from document text and validates against state regulatory requirements with clause-level citations.

Synchronous Deepgram audio intelligence workflow. It transcribes one explicit media URL, extracts utterances and channel alternatives when returned, and summarizes transcript quality, summary, topics, intents, sentiment, speakers, and follow-up actions. It never uploads files, opens streaming sockets, configures voice agents, generates tokens, uses callbacks, or calls arbitrary Deepgram routes.

Read-only Deepgram model inventory workflow. It lists public models and project-accessible models, tables STT and TTS availability, and summarizes model selection signals. It never creates keys, mutates projects, starts transcription, opens streaming, or calls arbitrary Deepgram routes.

Read-only Deepgram usage and balance workflow. It reads one project, usage fields, usage breakdown, and balances for the selected date range, then summarizes usage, feature mix, model mix, and outstanding balances. It never creates keys, changes members, mutates projects, exports purchases, creates self-hosted credentials, starts transcription, or calls arbitrary Deepgram routes.

Read-only Deepgram text intelligence workflow. It analyzes explicit pasted text for summary, sentiment, topics, and intents, then produces a compact brief. It never sends Deepgram a URL to fetch, uses callbacks, uploads files, opens streaming APIs, creates tokens, or calls arbitrary Deepgram routes.

Scans a HubSpot deal's logged activities (calls, emails, meetings, notes) for competitor mentions, searches the web for the named competitors' pricing + features, then produces a comparison analysis. Deal + activity reads bind to your HubSpot connection via the canonical deal.read + engagement.list ops; web search runs through an enrolled Exa connection's gated recued-core.exa.web.search op.

Analyzes showing patterns for potential steering violations under FHA (24 CFR §100.70). Computes chi-square steering score across inferred demographic proxies and zip clusters. Buyer names processed transiently by AI per inference requirements; never stored or exposed in output. Examples shown only when potential steering detected.

Weekday pipeline health digest with drift detection. Compares today's weighted pipeline score against yesterday's, flags deals that moved stages or went stale, and surfaces the overall health delta.

Approval-gated Microsoft Entra user disable workflow for one account. It reads the user for context, then calls recued-core.microsoft-entra.user.disable for exactly that user with accountEnabled=false. It does not delete users, reset passwords, mutate MFA, revoke sessions, assign licenses, change group memberships, or call arbitrary Graph APIs.

Scheduled read-only activity digest for one Discord guild channel. It reads guild and channel metadata, recent messages, pinned messages, active guild threads, and scheduled events through recued-core.discord, renders compact tables, and optionally sends an in-app nudge when messages are visible. It never posts, edits, deletes, pins, creates invites, creates threads, changes roles, changes guild or channel settings, or calls arbitrary Discord API routes.

Read-only AI-assisted brief for one Discord thread channel. It reads thread metadata, recent thread messages, pinned messages, and visible thread members through recued-core.discord, then summarizes discussion state, decisions, open questions, and follow-ups. It never posts, edits, reacts, pins, joins, leaves, archives, locks, or mutates the thread.

Scheduled adopter for DocuSign envelope closure rows seeded by send-docusign-template-envelope-with-closure. It lists only Recued-originated envelope watches, re-reads a bounded batch of envelope from DocuSign, and closes the shared row when DocuSign reports a terminal status. It can notify the owner on completion or exception status, but it never sends reminders, voids envelopes, changes recipients, downloads documents, creates Connect/webhook settings, or calls arbitrary DocuSign endpoints.

Read-only evidence brief for one DocuSign envelope. It reads envelope metadata, recipients, document metadata, audit events, and captured form data, then renders tables for review. It never downloads document binaries, signature images, or recipient ceremony URLs and does not mutate the envelope.

Scheduled status digest for one DocuSign account. It searches a bounded page of envelopes by status/date, renders a compact table, and optionally sends an in-app nudge when matching envelopes are present. Read-only: sending, voiding, recipient updates, template changes, binary downloads, and Connect administration stay outside this workflow.

Analyzes deal context and recent activity, then generates a personalized follow-up email draft and writes it into HubSpot's email compose form. Activities bind to your HubSpot connection via the canonical engagement.list op.

Read-only selected-message reply workflow. Loads one mail record, assembles the thread body when available, reads contact timeline context, classifies the support request, and drafts a plain-text reply without sending.

Read-only evidence brief for one Dropbox Sign signature request. It reads request metadata and signer status through recued-core.dropbox-sign, then asks the AI summarizer for completion state, signer blockers, expiration risk, template context, metadata signals, and concrete next steps. It never reminds signers, updates signers, cancels requests, downloads files, removes access, or calls arbitrary Dropbox Sign endpoints.

Scheduled read-only Dropbox Sign status digest. It lists a bounded page of signature requests, templates, and bulk-send jobs through recued-core.dropbox-sign, renders compact review tables, and optionally sends an in-app nudge when matching requests are visible. It never sends, cancels, updates signers, creates templates, downloads files, changes teams, or calls arbitrary Dropbox Sign endpoints.

Read-only template readiness brief for one Dropbox Sign template. It reads the template through recued-core.dropbox-sign, then summarizes signer roles, CC roles, custom fields, access metadata, and launch risks before a request is sent. It never creates, edits, deletes, uploads files to, sends from, or calls arbitrary Dropbox Sign endpoints.

Read-only ElevenLabs speech history item brief. It retrieves one explicit history item by ID through recued-core.elevenlabs and renders generation metadata, text, usage deltas, output format, and the raw history JSON for audit. It does not download audio, delete history, bulk-download history, regenerate speech, mutate voices/samples, configure agents/tools/MCP/secrets, or call arbitrary ElevenLabs routes.

Approval-gated ElevenLabs workflow for generating one text-to-speech response as JSON with base64 audio and character alignment timestamps. It reads the selected voice and default settings first, then calls recued-core.elevenlabs.speech.create with explicit text, model, output format, and voice settings. It does not download binary audio, stream output, upload audio, clone voices, train PVC voices, mutate voices or samples, configure agents/tools/MCP/secrets, or call arbitrary ElevenLabs routes.

Scheduled read-only ElevenLabs operations digest. It reads subscription usage and recent speech history metadata through recued-core.elevenlabs, renders compact review tables, and can send an in-app notification when history activity or open invoices are visible. It never generates audio, downloads history audio, deletes history, bulk-downloads history, mutates voices/samples, uploads audio, configures agents/tools/MCP/secrets, or calls arbitrary ElevenLabs routes.

Owner-visible list/close role for recued-core/figma-comment-reply-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.

Read-only ElevenLabs catalog brief. It reads account/subscription context, visible voices, model capabilities, and default voice settings through recued-core.elevenlabs, then renders compact tables for choosing a safe voice/model pair. It does not generate audio, download audio, stream output, mutate voices or samples, clone/train voices, configure agents/tools/MCP/secrets, or call arbitrary ElevenLabs routes.

Approval-gated Microsoft Entra user enable workflow for one account. It reads the user for context, then calls recued-core.microsoft-entra.user.enable for exactly that user with accountEnabled=true. It does not reset credentials, change MFA, assign licenses, change group memberships, or call arbitrary Graph APIs.

Always-approval-gated workflow to end the currently active conference in one Google Meet space. It reads the space first for context, then calls recued-core.google-meet.space.end_active_conference only when an active conference is present. It does not delete the space, edit settings, schedule Calendar events, download artifacts, or call arbitrary Google APIs.

Vendor-agnostic Layer-1 silent producer wrapping the `engagement_silence_duration` topic per spec § A.9.1. Subscribes to bus events from BOTH connection.api.hubspot.deal AND connection.api.salesforce.opportunity updates; for each fired record reads any housekeeping-computed row via `enrichment-list` with the dynamic `{{context.event.payload.platform}}` scope and re-emits it through the recipe cycle (so the row carries an up-to-date `cursor_at` reflecting the deal touch even when the substrate-side housekeeping cycle hasn't fired yet). The substrate-side housekeeping engagement-aggregates code (D-139 P1a.1 — `backend/server/src/housekeeping/engagement-aggregates/engagement-silence-duration.ts`) remains the canonical compute path; producer recipe writes carry `authored_by_recipe_id` distinct from the housekeeping `system.housekeeping.<topic>` author so both rows coexist on the unique `(topic, scope, target_id, authored_by_recipe_id)` index without conflict. Honest-zero defaults per the value-schema invariant when no housekeeping row exists yet.

Vendor-agnostic Layer-1 silent producer wrapping the `engagement_velocity_signal` topic per spec § A.9.1. Subscribes to bus events from BOTH connection.api.hubspot.deal AND connection.api.salesforce.opportunity updates; for each fired record reads any housekeeping-computed row via `enrichment-list` with the dynamic `{{context.event.payload.platform}}` scope and re-emits it through the recipe cycle so the row carries an up-to-date `cursor_at` reflecting the deal touch. The substrate-side housekeeping engagement-aggregates code (D-139 P3 — `backend/server/src/housekeeping/engagement-aggregates/engagement-velocity-signal.ts`) is the canonical compute path with the full Pass-4 evidence-quality fold (authorship + lifecycle + direction filters; 90d window split into recent 30d + baseline 60d; weighted trajectory math). Recipe writes carry `authored_by_recipe_id` distinct from the housekeeping `system.housekeeping.<topic>` author so both rows coexist on the unique `(topic, scope, target_id, authored_by_recipe_id)` index without conflict. Honest-zero `'steady'` default per the trajectory enum invariant when no housekeeping row exists yet.

Read-only Etsy listing readiness review. It reads one listing, its inventory document, media, digital files, properties, personalization, variation images, translation, shop sections, shipping profiles, seller taxonomy nodes, recent listing transactions, and recent shop reviews through recued-core.etsy, then asks the AI summarizer for listing readiness, shipping/catalog fit, inventory/media risks, review signals, and concrete next steps. It never updates listings, inventory, shipments, shop settings, images, files, refunds, buyer messages, payments, addresses, or arbitrary Etsy endpoints.

Read-only Etsy order support brief. It reads one receipt, its transactions, purchased listings, and attached payment records through recued-core.etsy, then asks the AI summarizer for fulfillment state, payment context, purchased item context, buyer-visible risks, and concrete next actions. It never updates shipments, listings, inventory, refunds, payment data, buyer addresses, shop settings, messages, files, images, or arbitrary Etsy endpoints.

Scheduled read-only Etsy seller digest. It reads shop metadata, shop sections, shipping profiles, return policies, production partners, holiday preferences, readiness state definitions, recent listings, open paid receipts, and recent reviews through recued-core.etsy, renders compact seller tables, and can send an in-app nudge when paid unshipped receipts are visible. It never updates listings, inventory, shipments, shop settings, refunds, buyer messages, images, files, payments, addresses, carts, favorites, profiles, or arbitrary Etsy endpoints.

Hidden event watcher for watch-for-expected-quotation-email. It matches a sender, subject, and body purpose deterministically, then moves the small linkage row to owner-visible needs_owner state. It never stores the source body, past-deal context, or a generated draft; review-expected-quotation-draft re-reads the source and generates an ephemeral draft on demand.

Approval-gated Canva export workflow. It reads one design and available export formats, then starts exactly one Canva export job through recued-core.canva.design.export.create. The export job can later return temporary download URLs; this recipe does not fetch or store those files, use print-partner exports, import designs, resize designs, or call arbitrary Canva endpoints.

Extract commitments from an inbound email into Recued's commitment tracker — who promised what to whom, with optional deadline and monetary amount. Thread-aware: a reply like 'yes, please send that by Friday' binds to the prior message, not the reply. Fires automatically on each inbound message; records only extractions above the confidence floor (default 0.7), resolves the counterparty to a known contact when possible, and the extractor model sees only PII-aliased text, never the raw sender.

Extracts contact details from email signatures. Shows extracted values with validation status. Includes actionable update button.

Analyzes HOA documents for rental caps, pet policies, age restrictions, and assessments. Flags critical buyer concerns.

Extracts key lease terms and validates against state landlord-tenant statutes with statutory citations. Reads the most recent NOTE on the deal as the lease document (via the canonical engagement.list op) and extracts the property's state from it.

Extract UTF-8 text from one trusted PDF through the local Poppler pdftotext CLI and preserve the captured text file. The recipe uses the recued-core.pdftotext fixed pdf.to_text operation: no shell, no arbitrary pdftotext flags, no caller-controlled output path, and PDF bytes stay behind file refs.

Extract action items from an inbound email into Recued's task tracker — title, due date, and priority (low / medium / high). Thread-aware; fires automatically on each inbound message; records only extractions above the confidence floor (default 0.7). A task is assigned to a contact only when the mail explicitly delegates it to a named third party — otherwise it lands unassigned. The extractor model sees only PII-aliased text, never the raw sender.

Scheduled adopter for Figma comment reply closure rows seeded by reply-figma-comment-with-closure. It lists only Recued-originated comment-reply watches, re-reads a bounded batch of Figma file's comments, and closes the shared row when Figma reports the watched root comment resolved or no longer returns it. It can notify the owner on resolution or disappearance, but it never creates, edits, deletes, or resolves comments, adds reactions, mutates files, exports images, configures webhooks, or calls arbitrary Figma endpoints.

Approval-gated template-fill workflow for one existing Google Docs document. It reads the target document for context, then replaces fixed placeholders such as [[CLIENT_NAME]] and [[SUMMARY]] through recued-core.google-docs.document.text.replace_all. It does not search Drive, share files, export documents, delete content, mutate styles/images/tables, or expose arbitrary Docs batchUpdate passthrough.

Approval-gated template-fill workflow for one existing Google Slides presentation. It reads the target deck for context, then replaces fixed placeholders such as [[CLIENT_NAME]] and [[SUMMARY]] through recued-core.google-slides.presentation.text.replace_all. It does not search Drive, share files, export presentations, delete slides, insert images/charts/tables/videos, or expose arbitrary Slides batchUpdate passthrough.

Searches recent news for each company behind contacts in target lifecycle stages, classifies the most significant event per account in one batch AI call, and shows a confidence-sorted table. CRM contacts bind to your HubSpot connection via the canonical contact.search op; web search runs through an enrolled Exa connection's gated recued-core.exa.web.search op.

Find CRM contacts with no phone number on file and show the count plus a follow-up table (email, lifecycle stage, owner). The missing-phone filter runs server-side in the CRM. Vendor-neutral: binds to HubSpot or Salesforce contacts at pack install.

Identifies high-ICP accounts with no recent outbound activity for re-engagement.

Identifies open deals with no activity beyond threshold and displays stalest deals first.

Scheduled read-only Firecrawl operations digest. It lists active crawls, reads credit and token usage, renders compact operations tables, and can send an in-app notification for active crawls or low remaining credits. It never starts or cancels jobs, registers webhooks, scrapes pages, mutates billing/team settings, or calls arbitrary Firecrawl API routes.

Read-only Firecrawl page extraction workflow. It scrapes one explicit URL through recued-core.firecrawl.page.scrape, summarizes the returned markdown and metadata, and shows key extraction counters. It never starts crawl jobs, runs browser actions, sends custom headers/cookies, bypasses TLS verification, registers webhooks, or calls arbitrary Firecrawl API routes.

Read-only Firecrawl research workflow. It searches web/news results through recued-core.firecrawl.web.search, renders result tables, and summarizes the returned titles, URLs, snippets, markdown, and warnings. It never starts crawl jobs, scrapes arbitrary routes directly, runs browser actions, sends custom headers/cookies, registers webhooks, or calls arbitrary Firecrawl API routes.

Optionally seed the owner's Recued-native operating system with a setup profile note, setup project, setup tasks, and weekly owner-review commitment. Defaults to preview; switch write_mode to create when the owner wants records written.

Show the owner what must be decided before Recued can run as a visible operating system: business profile, owner identity, external service lanes, inbox, calendar, weekly review cadence, and follow-up default. This recipe is read-only and intentionally does not pretend to inspect connection state.

Read-only runtime brief for one Fly.io app. It reads the app, machines, volumes, certificates, IP assignments, and platform regions through recued-core.flyio, then asks the AI summarizer for health, capacity, certificate/DNS posture, and next operational checks. It never creates, starts, stops, restarts, suspends, deletes, executes commands, mutates secrets, mints tokens, or calls arbitrary Fly.io API routes.

Scheduled read-only digest for Fly.io operations. It reads current token metadata, apps, organization-wide machines, organization-wide volumes, and platform regions through recued-core.flyio, renders compact tables, and can send an in-app nudge when machines or volumes are visible. It never creates, starts, stops, restarts, suspends, cordons, deletes, executes commands, mutates secrets, mints tokens, changes IP assignments, or calls arbitrary Fly.io API routes.

Read-only investigation brief for one Fly.io Machine. It reads the machine, recent events, process list, memory, metadata, and versions through recued-core.flyio, then asks the AI summarizer for runtime state, recent lifecycle signal, process pressure, memory posture, configuration risk, and next checks. It never starts, stops, restarts, suspends, deletes, executes commands, sends signals, mutates metadata or secrets, or calls arbitrary Fly.io API routes.

Read-only Email/Outbox workflow. Scans a sent/outbound mail folder, classifies likely follow-up candidates, and drafts a small batch of plain-text replies without sending. Use this as the preview lane before running batch-approve-followups.

Checks if contact follow-up is overdue based on last activity date.

Checks days since last activity on contact/deal/ticket and shows overdue status or missing data.

Roll your open CRM pipeline into one forecast card: open-deal count, raw pipeline value (sum of amounts), and the vendor's committed forecast (sum of forecast amounts). Vendor-neutral: binds to HubSpot deals or Salesforce opportunities at pack install; 'open' is the canonical close_state signal, not a raw vendor stage.

Groups open deals by close date month within forecast horizon, displays monthly pipeline table, and generates AI narrative analyzing monthly trends + risk factors.

Forecasts pipeline by month with weighted totals and AI narrative.

Scheduled adopter for Freshdesk ticket reply closure rows seeded by reply-freshdesk-ticket-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of ticket from Freshdesk, and closes or flags the shared row when Freshdesk reports a configured closure or owner-actionable status. It can notify the owner on closure or customer-return states, but it never updates tickets, replies to customers, creates private notes, creates or edits automations/dispatch rules/SLA/admin settings, deletes records, or calls arbitrary Freshdesk endpoints.

Read-only AI-assisted review brief for one Freshdesk ticket. It reads the ticket, full conversation list, requester contact when available, company when available, time entries, and matching solution articles through recued-core.freshdesk, then summarizes the customer ask, urgency, history, support risk, and next response. It never replies, updates, deletes, bulk-mutates, attaches files, changes automations/admin settings, or calls arbitrary Freshdesk endpoints.

Scheduled read-only digest for a Freshdesk support queue. It reads the current agent, groups, matching tickets, ticket fields, and matching solution articles through recued-core.freshdesk, renders compact support tables, and can send an in-app nudge when matching tickets exist. It never creates, replies, updates, deletes, bulk-mutates, attaches files, changes automations/admin settings, or calls arbitrary Freshdesk endpoints.

Read-only AI-assisted brief for one Front conversation. It reads conversation metadata, messages, internal comments, events, followers, and inboxes through recued-core.front, then summarizes customer context, issue state, suggested next reply, and operational follow-ups. It never sends replies, posts comments, changes status, tags, assignees, contacts, or knowledge base content.

Scheduled adopter for Front conversation reply reopen rows seeded by reply-front-conversation-with-reopen-watch. It lists only Recued-originated public-reply watches, re-reads a bounded batch of Front conversation and its latest events, and closes or flags the shared row when Front reports a terminal status, resolved ticket category, newer customer-return event, reopen event, or delivery error. It can notify the owner on closure or owner-actionable states, but it never updates conversations, sends replies, creates comments, creates reminders, mutates tags or custom fields, creates or edits Front Rules, changes inbox/admin settings, creates webhooks or application triggers, deletes records, bulk mutates, or calls arbitrary Front endpoints.

Scheduled read-only triage digest for one Front inbox. It reads inbox metadata, matching conversations, visible teammates, and tags through recued-core.front, renders compact tables, and optionally sends an in-app nudge when conversations are visible. It never sends replies, changes assignees, changes statuses, creates tags, updates contacts, mutates knowledge base content, deletes data, downloads attachments, or calls arbitrary Front API routes.

Approval-gated Squarespace fulfillment workflow. It reads the target order, then fulfills exactly one order with caller-supplied shipment rows and optional customer notification through recued-core.squarespace. It does not create orders, refund payments, edit products, mutate inventory directly, delete data, or call arbitrary endpoints.

Generates executive-ready case studies from closed-won deal notes with PII protection. Activities bind to your HubSpot connection via the canonical engagement.list op.

Generates three tailored cold emails (initial, follow-up, breakup) using account context. Each email ≤150 words with copy buttons.

Generates a personalized icebreaker for a CRM contact using recent web news about their company. Contact reads bind to your HubSpot connection via the canonical contact.read op; web search runs through an enrolled Exa connection's gated recued-core.exa.web.search op.

Generates a professional 4-section meeting agenda when a deal has a meeting scheduled within 48 hours. Activities bind to your HubSpot connection via the canonical engagement.list op.

A scheduled worktree watch for one trusted local Git repository path. It uses the repo.changed_files op as an empty/non-empty trigger signal, skips the heavier status/log reads when the worktree is clean, and renders a compact card when local changes are present. It never fetches, pulls, pushes, clones, shells out, or talks to a remote.

A scheduled local Git briefing for one trusted repository path. During the configured work-hours window it reads branch/status rows and recent commits through the recued-core.git CLI pack, then renders a compact card. It never fetches, pulls, pushes, clones, shells out, or talks to a remote.

Scheduled read-only digest for the authenticated GitHub user. It reads the current user, open assigned issues, and unread notification threads through recued-core.github-pack, renders compact triage tables, and can send an in-app nudge when assigned work or notifications exist. It never creates or updates issues, comments, pull requests, branches, releases, workflow runs, checks, secrets, collaborators, admin settings, webhooks, or arbitrary GitHub APIs.

Scheduled adopter for GitHub issue closure rows seeded by create-github-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of GitHub issue, and closes the shared row when GitHub reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, transfers, labels, assigns, locks, comments on, creates pull requests for, or otherwise mutates GitHub issues.

Scheduled adopter for GitHub issue comment closure rows seeded by comment-github-issue-with-closure. It lists only Recued-originated issue-comment watches, re-reads a bounded batch of GitHub issue, and closes the shared row when GitHub reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, transfers, labels, assigns, locks, comments on, or otherwise mutates GitHub issues.

Scheduled detection half of the GitHub Actions to Linear exception handoff loop. It reads recent failed workflow runs for one configured repository, excludes pull-request-attached runs by default, fetches failed job names for the first unhandled non-PR run, writes one data.shared proposal, and notifies the owner to review whether the failed run should become Linear work. It never creates Linear issues, comments on GitHub, reruns workflows, updates GitHub issues or pull requests, changes branch protection, mutates Linear projects, or calls arbitrary APIs. GitHub Actions notifications, workflow logs, rerun controls, branch protection, Linear Reviews, Linear's GitHub integration, and GitHub issue syncing own their normal paths; this recipe only creates a Recued-visible exception proposal that an owner can approve or dismiss with create-approved-linear-issue-from-github-run.

Scheduled feedback half of the GitHub Actions to Linear exception handoff loop. It reads Linear issues created by create-approved-linear-issue-from-github-run, reads the original GitHub workflow run for current context, closes the Recued data.shared handoff when the Linear issue reaches a terminal state, and optionally notifies the owner to verify the current CI state. It does not update GitHub, rerun workflows, comment on GitHub, update Linear issues, create comments, change branch protection, or call arbitrary APIs. Linear Reviews, GitHub Actions notifications, logs, reruns, branch protection, Linear's GitHub integration, and GitHub issue syncing own normal CI operations; this watcher only records Recued-visible exception closure.

Read-only review brief for one GitHub pull request. It reads repository metadata, pull request details, changed files, reviews, review comments, recent workflow runs for the PR head branch, and check runs for the PR head SHA through recued-core.github-pack, then asks the AI summarizer for impact, reviewer state, CI status, risks, and next actions. It never creates or updates issues, comments, pull requests, branches, releases, workflow runs, checks, secrets, collaborators, admin settings, webhooks, or arbitrary GitHub APIs.

Scheduled adopter for GitLab issue note closure rows seeded by comment-gitlab-issue-with-closure. It lists only Recued-originated issue-note watches, re-reads a bounded batch of GitLab issue, and closes the shared row when GitLab reports that issue closed. It can notify the owner on closure, but it never creates, updates, closes, reopens, deletes, moves, labels, assigns, comments on, or otherwise mutates GitLab issues.

Read-only review brief for one GitLab.com merge request. It reads project metadata, merge request details, discussion notes, recent commits on the source branch, and pipelines for that branch through recued-core.gitlab, then asks the AI summarizer for scope, reviewer state, CI status, risks, and next actions. It never creates or updates issues, notes, merge requests, branches, tags, commits, releases, runners, admin settings, pipelines, jobs, artifacts, webhooks, or arbitrary GitLab APIs.

Scheduled read-only digest for one GitLab.com project. It reads the current user, project metadata, open issues, opened merge requests, recent pipelines, and releases through recued-core.gitlab, renders compact triage tables, and can send an in-app nudge when active project work is visible. It never creates or updates issues, notes, merge requests, branches, tags, commits, releases, runners, admin settings, pipelines, jobs, artifacts, webhooks, or arbitrary GitLab APIs.

Scheduled read-only digest for one Gmail mailbox. It reads the mailbox profile, labels, matching inbox threads, unread messages, draft IDs, send-as identities, and vacation responder state through recued-core.gmail, renders compact tables, and can send an in-app nudge when visible mail needs attention. It never sends mail, creates or sends drafts, mutates labels, changes filters, changes settings, deletes, trashes, imports, watches Pub/Sub, or calls arbitrary Gmail APIs.

Read-only review brief for one Gmail thread. It reads the full parsed thread, optional selected-message metadata, mailbox labels, drafts, send-as identities, and vacation responder state through recued-core.gmail, then asks the AI summarizer for participants, urgency, commitments, open questions, risks, and next actions. It never sends mail, creates or sends drafts, mutates labels, changes filters, changes settings, deletes, trashes, imports, watches Pub/Sub, or calls arbitrary Gmail APIs.

Scheduled morning agenda for one Google Calendar. It reads calendar metadata, today's event window, and free/busy blocks through recued-core.google-calendar, renders a compact agenda, and can send an in-app nudge when events are present. Read-only: event creation, edits, and cancellation stay behind the pack's approval-gated write operations.

Read-only prep brief for one Google Calendar event. It reads calendar metadata and event details through recued-core.google-calendar, then asks the AI summarizer for agenda, attendees, open questions, and next actions. It never creates, updates, deletes, imports, shares, or calls arbitrary Google Calendar APIs.

Scheduled read-only activity digest for one Google Chat space. It reads space context, a bounded page of recent messages, members, and recent space events through recued-core.google-chat, renders compact tables, and optionally sends an in-app nudge when messages are visible. It never sends Chat messages, changes memberships, downloads attachment bytes, edits read-state, or calls arbitrary Chat APIs.

Read-only review brief for one Google Chat message thread. It reads the space, the seed message, messages in the same thread, and reactions on the seed message through recued-core.google-chat, then asks the AI summarizer for decisions, blockers, named owners, and next steps. It never sends replies, edits messages, changes reactions, downloads attachments, changes memberships, or calls arbitrary Chat APIs.

Read-only review brief for one Google Docs document. It reads a single document through recued-core.google-docs and asks the AI summarizer for a concise summary, decisions, risks, and next actions. It never creates, edits, deletes, exports, shares, comments on, or searches Drive files.

Scheduled adopter for Google Drive file comment closure rows seeded by comment-google-drive-file-with-closure. It lists only Recued-originated file-comment watches, re-reads a bounded batch of Drive comment thread, and closes the shared row when Google Drive reports that comment resolved or deleted. It can notify the owner on resolution or deletion, but it never creates, edits, deletes, or resolves comments, changes file permissions, mutates document body content, downloads files, moves files, configures Drive notifications, or calls arbitrary Google Drive endpoints.

Read-only post-meeting brief for one Google Meet conference record. It reads the conference record, participants, optional recording metadata, optional transcript metadata, and optional transcript entries through recued-core.google-meet, then asks the AI summarizer for attendance, decisions, risks, follow-ups, artifact links, and next actions. It never downloads Drive recordings, fetches Docs transcript files, edits Meet spaces, ends live calls, schedules Calendar events, or calls arbitrary Google APIs.

Read-only review brief for one Google Slides presentation. It reads a single deck through recued-core.google-slides, gets one first-slide thumbnail when available, and asks the AI summarizer for audience, narrative, gaps, risks, and next actions. It never creates, edits, deletes, exports, shares, or searches Drive files.

Read-only engagement brief for one Klaviyo profile. It reads the profile, recent events, lists, and segments through recued-core.klaviyo, then asks the AI summarizer for customer context, recent behavior, subscription/list posture, and safe follow-up ideas. It never creates, updates, merges, suppresses, unsubscribes, sends, schedules, or mutates Klaviyo records.

Scheduled adopter for Google Tasks task closure rows seeded by create-google-task-with-closure. It lists only Recued-originated Google Task watches, re-reads a bounded batch of Google Task, and closes the shared row when Google Tasks reports completion. Rows that cannot be read remain open instead of closing from cached state. It can notify the owner on completion, but it never creates, updates, completes, deletes, moves, reorders, renames lists, mutates links, touches hidden/deleted or assignment-source fields, clears completed tasks, or otherwise mutates Google Tasks.

Scheduled morning task plan for one Google Tasks list. It reads tasks due today through the recued-core.google-tasks capability pack, renders a compact table, and optionally sends an in-app nudge when due tasks are present. Read-only: task creation, completion, edits, and moves stay behind the pack's approval-gated write operations.

Read-only Greenhouse candidate brief. It fetches selected candidates plus related applications, interviews, scorecards, and offers through recued-core.greenhouse, then asks core.ai.summarize for a compact recruiting evidence brief. It does not write notes, create candidates, move applications, change offers, upload attachments, or call arbitrary Greenhouse endpoints.

Read-only Greenhouse job pipeline brief. It fetches selected jobs plus applications, openings, job posts, interviews, and offers through recued-core.greenhouse, then asks core.ai.summarize for a compact readiness view for hiring managers and recruiting ops. It does not mutate jobs, openings, posts, candidates, applications, offers, attachments, or arbitrary Greenhouse endpoints.

Scheduled read-only Greenhouse Harvest v3 recruiting digest. It lists bounded pages of open jobs, active applications, candidates, interviews, offers, offices, and departments through recued-core.greenhouse, renders compact review tables, and optionally sends an in-app nudge when active applications are visible. It never creates candidates, writes notes, moves applications, changes offers, mutates jobs or openings, uploads attachments, or calls arbitrary Greenhouse endpoints.

Low-latency Groq chat workflow. It reads the selected model metadata, creates one non-streaming chat completion from an explicit question, and summarizes answer quality, finish reason, model, and token usage. It never enables streaming, tools, tool_choice, functions, MCP tools, Compound custom tool configuration, web-search settings, audio, files, or arbitrary Groq routes.

Read-only Groq embedding workflow. It creates embeddings for explicit caller-provided text samples and summarizes vector count, encoding, token usage, and readiness for semantic search or RAG. It never sends files, calls audio endpoints, uses tools, creates batch jobs, or uses arbitrary Groq routes.

Read-only Groq operations workflow. It lists models, batch jobs, and file metadata visible to the enrolled connection, tables operational state, and summarizes model availability, batch backlog, and file inventory. It never creates or cancels batches, uploads/downloads/deletes files, deletes models, calls fine tuning, or uses arbitrary Groq routes.

Groq Responses API workflow. It creates one bounded non-streaming text response, tables output items, and summarizes response status, generated content, reasoning metadata, and token usage. It never enables tools, tool_choice, parallel tool calls, streaming, storage, metadata, previous responses, audio, files, or arbitrary Groq routes.

Groups US accounts into 5 regions (Northeast, Midwest, South, West, Other) using zip code prefix lookup. Computes account count, total revenue, and average deal size per region. Table sorted by revenue descending.

Groups all open deals by owner with pipeline metrics and sortable table view.

D-179 worked example, stage 4 (the failure/stall handler). Lists codex_queue rows in state fail or fail_timeout, emails the failure kind (non-zero exit vs no evidence before the timeout - the silent/stalled case), and finalizes each row to failed_notified. File-free: the sweeper owns marker consumption. A late marker after a timeout would be reconciled by a later sweep, so an occasional follow-up success notification is expected (at-least-once by design). Run this as ONE scheduled dish - the scheduler serializes a schedule's runs, so the list-notify-mark sequence is not raced by a concurrent copy of itself.

D-179 worked example, stage 3 (the success handler). Lists codex_queue rows in state=success, emails the issue link plus the log path, and finalizes each row to done. The sweeper already consumed the completion marker, so this stage is file-free. Notify-then-mark is at-least-once: a crash between them re-notifies next cycle. Run this as ONE scheduled dish - the scheduler serializes a schedule's runs, so the list-notify-mark sequence is not raced by a concurrent copy of itself.

Scheduled adopter for Help Scout conversation reply closure rows seeded by reply-helpscout-conversation-with-closure. It lists only Recued-originated public-reply watches, re-reads a bounded batch of conversation from Help Scout, and closes or flags the shared row when Help Scout reports a configured closure or owner-actionable status. It can notify the owner on closure or customer-return states, but it never updates conversations, replies to customers, creates internal notes, creates or edits Help Scout Workflows, changes mailbox/admin settings, creates webhooks, deletes records, bulk mutates, or calls arbitrary Help Scout endpoints.

Read-only AI-assisted review brief for one Help Scout conversation. It reads the conversation, its thread history, primary customer profile, and team context through recued-core.helpscout, then summarizes customer ask, latest state, sentiment, support risk, and next response. It never replies, notes, updates tags or custom fields, mutates users or inbox settings, downloads attachments, deletes, bulk-mutates, runs workflows, or calls arbitrary Help Scout endpoints.

Scheduled read-only digest for one Help Scout inbox. It reads inbox metadata, folders, matching conversations, users, and tags through recued-core.helpscout, summarizes the support queue, renders compact triage tables, and can send an in-app nudge when conversations match. It never creates, replies, notes, updates tags or custom fields, mutates users or inbox settings, downloads attachments, deletes, bulk-mutates, runs workflows, or calls arbitrary Help Scout endpoints.

Scheduled read-only Heroku app operations digest. It reads one app, dynos, formations, releases, builds, domains, add-ons, and pipeline coupling through recued-core.heroku, renders compact review tables, and can send an in-app nudge when runtime or release records are visible. It never creates, restarts, stops, scales, rolls back, mutates config vars, provisions add-ons, creates log sessions, deletes resources, or calls arbitrary Heroku API routes.

Read-only runtime brief for one Heroku app. It reads the app, dynos, formation, releases, builds, domains, add-ons, pipeline coupling, and available dyno sizes through recued-core.heroku, then asks the AI summarizer for runtime health, release posture, DNS status, scaling context, and concrete next checks. It never creates, restarts, stops, scales, rolls back, mutates config vars, provisions add-ons, creates log sessions, deletes resources, or calls arbitrary Heroku API routes.

Read-only investigation brief for one Heroku release. It reads the target release, neighboring release/build/runtime/domain context, and asks the AI summarizer for what changed, rollback eligibility, likely operational impact, and next checks. It never creates builds, rolls back, restarts or stops dynos, scales formation, mutates config vars, deletes resources, or calls arbitrary Heroku API routes.

Scheduled read-only Hugging Face research digest. It reads Daily Papers, recent Paper Pages, and documentation search context through recued-core.huggingface, summarizes notable AI research items, and can send an in-app notification when papers are visible. It never comments on papers, claims papers, mutates links, creates collections or discussions, downloads files, or calls arbitrary Hugging Face routes.

Read-only Hugging Face Hub discovery workflow. It searches Hub resources, trending items, documentation snippets, and Spaces hardware through recued-core.huggingface, then summarizes useful models, datasets, Spaces, papers, and collections for a requested topic. It never creates repositories, writes discussions or collections, downloads files, reads token endpoints, mutates settings, or calls arbitrary Hugging Face routes.

Read-only Hugging Face model repository review workflow. It reads refs, recent commits, security scan status, selected tree entries, and repository discussions through recued-core.huggingface, then summarizes release and adoption readiness for a model repository. It never creates discussions, commits, branches, tags, repositories, downloads files, reads token endpoints, mutates settings, or calls arbitrary Hugging Face routes.

Vendor-agnostic Layer-1 silent producer wrapping the `inbound_outbound_ratio` topic per spec § A.9.1. Subscribes to bus events from BOTH connection.api.hubspot.deal AND connection.api.salesforce.opportunity updates; for each fired record reads any housekeeping-computed row via `enrichment-list` with the dynamic `{{context.event.payload.platform}}` scope and re-emits it through the recipe cycle. The substrate-side housekeeping engagement-aggregates code (D-139 P3 — `backend/server/src/housekeeping/engagement-aggregates/inbound-outbound-ratio.ts`) is the canonical compute path with the full Pass-4 evidence-quality fold (inbound = direction='inbound' + authorship excluding automation/system_process; outbound = direction='outbound' + authorship IN user/crm_user; failed sends + no_answer count toward outbound effort but never as prospect engagement). Recipe writes carry `authored_by_recipe_id` distinct from the housekeeping `system.housekeeping.<topic>` author so both rows coexist on the unique `(topic, scope, target_id, authored_by_recipe_id)` index without conflict. Honest-zero `'mutual'` default per the bucket enum invariant when no housekeeping row exists yet.

Read-only follow-up triage brief for one incident.io incident or assignee team. It reads follow-ups, actions, teams, users, and optional incident context through recued-core.incidentio, then asks the AI summarizer for owners, blocked work, aging risk, duplicate work, and next steps. It never creates, updates, completes, deletes, or exports follow-ups, actions, incidents, schedules, escalations, settings, or arbitrary incident.io API routes.

Read-only incident command brief for one incident.io incident. It reads the incident, incident updates, actions, follow-ups, users, and teams through recued-core.incidentio, then asks the AI summarizer for status, owner context, decisions, open work, risks, and next steps. It never creates or edits incidents, actions, follow-ups, schedules, escalations, settings, API keys, or arbitrary incident.io API routes.

Scheduled read-only digest for incident.io operations. It reads API-key identity, incidents, actions, follow-ups, schedules, and escalations through recued-core.incidentio, renders compact tables, and can send an in-app nudge when active incident or escalation records are visible. It never creates or edits incidents, actions, follow-ups, schedules, escalations, status pages, catalog entries, settings, API keys, or arbitrary incident.io API routes.

Cross-entity view: deal health, contact engagement, company context, recent activities, and open tickets — all in one sidebar. AI synthesizes the full picture. Activities bind to your HubSpot connection via the canonical engagement.list op.

Scheduled adopter for Intercom conversation reply closure rows seeded by reply-intercom-conversation-with-closure-watch. It lists only Recued-originated public-reply watches, re-reads a bounded batch of Intercom conversation, and closes or flags the shared row when Intercom reports configured closure state or customer-waiting owner-review state after the Recued reply. It can notify the owner on closure or owner-actionable customer-return states, but it never replies, adds notes, closes, reopens, snoozes, assigns, tags, mutates contacts or companies, creates or updates tickets, configures Intercom Workflows or Rules, creates webhooks, deletes records, bulk mutates, or calls arbitrary Intercom endpoints.

Read-only review brief for one Intercom conversation and optional contact. It reads the conversation, contact profile, contact notes, companies, tags, admins, teams, workspace tags, and matching Help Center articles through recued-core.intercom, then asks the AI summarizer for urgency, customer context, likely resolution path, knowledge-base matches, risks, and next actions. It never replies, assigns, closes, snoozes, tags, mutates contacts or companies, creates or updates tickets, deletes, redacts, publishes articles, changes admin settings, or calls arbitrary Intercom APIs.

Scheduled read-only triage digest for Intercom. It reads admins, teams, recent conversations, open conversations, workspace tags, and matching Help Center articles through recued-core.intercom, renders compact support tables, and can send an in-app nudge when open conversations are visible. It never replies, assigns, closes, snoozes, tags, mutates contacts or companies, creates or updates tickets, deletes, redacts, publishes articles, changes admin settings, or calls arbitrary Intercom APIs.

Chronologically sorts all deal activities and generates AI-powered timeline summary highlighting key compliance decisions. Activities bind to your CRM connection via the canonical engagement.list op (HubSpot engagements).

Approval-gated Clerk organization invitation workflow for one invitee. It reads the organization and existing matching invitations for context, then calls recued-core.clerk.organization.invitation.create with one email address and role. It does not create users, bulk invite, revoke invitations, mutate roles or permissions, change domains, or call arbitrary Clerk APIs.

Approval-gated WorkOS invitation workflow. It reads the destination organization, checks matching existing users and invitations by email, sends exactly one invitation through recued-core.workos, and returns the invite result. It never creates users, updates memberships, revokes invitations, deletes records, authenticates users, exchanges tokens, exports audit logs, or calls arbitrary WorkOS APIs.

Parse a received invoice or receipt (PDF / image / DOCX / scan) with the local docling tool into readable text - so any text model can read it - then extract vendor, number, amount, currency, and dates. Preview-first: shows the extracted fields and writes nothing; set write_mode to stage to persist a staged invoice/expense row into data.shared. Writes no accounting system - staging is the holding area for later review and posting. Content-isolated via Gateway-gated file refs.

Watch a Google Drive folder for new invoice / receipt documents and stage their extracted finance data. Polls the folder via the gdrive file.list operation, picks the newest document that is not a Google-native file, downloads its bytes straight into the warehouse CAS as a Gateway-gated data.file (file.download surfaces result.file_ref, so the bytes never flow through op-step values), parses it to Markdown with the local docling tool (which materializes the file_ref to a temp file it reads), and pulls vendor, number, amount, currency, and dates from the parsed Markdown via the same file-ref isolation. Preview-first: by default it shows the extracted fields and writes nothing; set write_mode to stage to persist a durable staged invoice/expense row into data.shared for later review and posting. A per-run context guard skips re-processing the same newest file across polls. This is the Drive-folder source lane for the SMB-finance intake; the manual single-document lane is invoice-intake-organizer.

Approval-gated Microsoft Defender for Endpoint machine isolation workflow for one machine. It reads the machine and related alerts for context, then calls recued-core.microsoft-defender-endpoint.machine.isolate for exactly that machine. It does not run live response, offboard devices, run antivirus scans, quarantine files, collect packages, mutate tags, create indicators, bulk-update alerts, or call arbitrary Defender APIs.

Scheduled adopter for Jira issue closure rows seeded by create-jira-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of Jira issue, and closes the shared row when Jira reports that issue has reached the Done status category. It can notify the owner on closure, but it never creates, updates, transitions, assigns, deletes, attaches to, links, watches, votes on, comments on, adds worklogs to, or otherwise mutates Jira issues.

Scheduled adopter for Jira issue comment closure rows seeded by comment-jira-issue-with-closure. It lists only Recued-originated issue-comment watches, re-reads a bounded batch of Jira issue, and closes the shared row when Jira reports that issue has reached the Done status category. It can notify the owner on closure, but it never creates, updates, transitions, assigns, deletes, attaches to, links, watches, votes on, comments on, or otherwise mutates Jira issues.

Read-only review brief for one Jira issue. It reads issue details, comments, worklogs, and available transitions through recued-core.jira, then asks the AI summarizer for status, blockers, owners, and next actions. It never comments, transitions, assigns, edits, deletes, attaches files, or calls arbitrary Jira endpoints.

Scheduled read-only digest for personal Jira work. It reads the current Jira user, assigned issues, optionally reported issues, and optionally recently updated issues through recued-core.jira, renders a compact table, and can send an in-app nudge when matching issues exist. It does not create, edit, transition, assign, delete, attach, notify, or call arbitrary Jira endpoints.

Read-only Jotform form readiness brief. It reads one form, questions, reports, uploaded-file metadata, and webhook registrations through recued-core.jotform, then asks the AI summarizer for launch readiness, intake quality, reporting coverage, webhook evidence, and operational risks. It never mutates forms, submissions, questions, reports, files, webhooks, folders, labels, or settings.

Scheduled read-only Jotform intake digest. It reads the current account, one form, recent submissions, reports, and account usage through recued-core.jotform, renders compact review tables, and optionally sends an in-app nudge when submissions are visible. It never creates, updates, deletes, clones, downloads files, mutates webhooks, changes account settings, or calls arbitrary Jotform endpoints.

Read-only Jotform submission review brief. It reads one form, that form's questions, and one submission through recued-core.jotform, then asks the AI summarizer for answer themes, routing signals, missing details, and concrete follow-up next steps. It never mutates forms, questions, submissions, webhooks, reports, files, settings, folders, or labels.

Read-only Klarna payment-session brief. It retrieves one payment session through recued-core.klarna, summarizes checkout readiness, cart totals, session status, and available Klarna payment method categories, and never mutates payment sessions, creates orders, cancels authorizations, or calls arbitrary endpoints.

Scheduled read-only digest for Klaviyo email marketing performance. It reads campaigns, flows, metrics, and campaign/flow values reports through recued-core.klaviyo, renders compact tables, and can send an in-app nudge when recent campaigns are visible. It never creates profiles, updates lists, turns flows on or off, sends campaigns, cancels sends, records events, mutates catalog, or calls arbitrary Klaviyo endpoints.

Vendor-agnostic Layer-1 silent producer wrapping the `last_meaningful_touch` topic per spec § A.9.1. Subscribes to bus events from BOTH connection.api.hubspot.deal AND connection.api.salesforce.opportunity updates; for each fired record reads any housekeeping-computed row via `enrichment-list` with the dynamic `{{context.event.payload.platform}}` scope and re-emits it through the recipe cycle. The substrate-side housekeeping engagement-aggregates code (D-139 P3 — `backend/server/src/housekeeping/engagement-aggregates/last-meaningful-touch.ts`) is the canonical compute path with the full Pass-4 evidence-quality fold (excludes tracking-pixel + workflow auto-logs via authorship NOT IN crm_automation/system_process; lifecycle filter point_in_time + completed only; direction-agnostic — any meaningful inbound or outbound counts). Recipe writes carry `authored_by_recipe_id` distinct from the housekeeping `system.housekeeping.<topic>` author so both rows coexist on the unique `(topic, scope, target_id, authored_by_recipe_id)` index without conflict. Honest-zero defaults per the value-schema invariant (last_touch_at = 0 paired with all-null vendor + entity + authorship + direction) when no housekeeping row exists yet — the value-schema validator enforces the pairing.

Read-only brief for one LaunchDarkly feature flag in one environment. It reads the project, environment, flag, flag status, and recent audit log entries through recued-core.launchdarkly, then asks the AI summarizer for release context, current posture, recent changes, risks, and next safe action. It never turns the flag on or off, changes targeting, creates flags, reviews approvals, or mutates LaunchDarkly records.

Scheduled read-only digest for one LaunchDarkly project environment. It reads the project, environment, feature flags, flag statuses, and recent audit log entries through recued-core.launchdarkly, renders compact tables, and can send an in-app nudge when matching flags or changes are visible. It never creates flags, turns flags on or off, edits targeting, reviews approvals, changes segments, or calls arbitrary LaunchDarkly APIs.

Read-only Lever opportunity brief. It fetches one opportunity plus related notes, interviews, feedback, offers, and panels through recued-core.lever, then asks core.ai.summarize for a compact recruiting evidence brief. It does not write notes, create opportunities, move stages, archive, change offers, create panels or interviews, download files, or call arbitrary Lever endpoints.

Read-only Lever posting pipeline brief. It fetches a selected posting, matching opportunities, users with posting access, stages, tags, sources, and requisitions through recued-core.lever, then asks core.ai.summarize for a compact readiness view for hiring managers and recruiting ops. It does not mutate postings, requisitions, users, opportunities, offers, interviews, files, or arbitrary Lever endpoints.

Scheduled read-only Lever recruiting digest. It lists bounded pages of opportunities, postings, stages, users, sources, tags, and requisitions through recued-core.lever, renders compact review tables, and optionally sends an in-app nudge when opportunities are visible. It never creates opportunities, writes notes, moves opportunities, updates postings, changes offers, uploads files, downloads resumes or offers, or calls arbitrary Lever endpoints.

Scheduled adopter for Linear issue closure rows seeded by create-linear-issue-with-closure. It lists only Recued-originated issue watches, re-reads a bounded batch of Linear issue, and closes the shared row when Linear reports the issue completed or canceled. It can notify the owner on terminal issue state, but it never creates, updates, moves, cancels, completes, deletes, archives, assigns, labels, subscribes to, comments on, or otherwise mutates Linear issues.

Scheduled adopter for Linear issue comment closure rows seeded by comment-linear-issue-with-closure. It lists only Recued-originated issue-comment watches, re-reads a bounded batch of Linear issue, and closes the shared row when Linear reports the issue completed or canceled. It can notify the owner on terminal issue state, but it never creates, updates, moves, cancels, completes, deletes, archives, assigns, labels, subscribes to, comments on, or otherwise mutates Linear issues.

Read-only review brief for one Linear issue and project. It reads issue details, project details, issue comments, project updates, active cycle context, and labels through recued-core.linear, then asks the AI summarizer for status, blockers, owners, stale signals, and next actions. It never creates, updates, moves, comments on, labels, archives, deletes, or calls arbitrary Linear GraphQL.

Scheduled read-only digest for personal Linear work. It reads the current user, assigned issues, optionally created issues, optionally blocked issues, active and next cycles, and open projects through recued-core.linear, renders compact tables, and can send an in-app nudge when matching issues exist. It does not create, update, move, delete, archive, comment on, label, subscribe to, or call arbitrary Linear GraphQL.

Lists recently closed lost deals with loss reasons, sorted newest first.

Lists recently closed lost deals with loss reasons, sorted by closure date.

Lists deals created in the last N days sorted by amount (descending).