fastn-ai
- 5 skills
- 0 followers
- 14 hours ago last updated
- ▌ Gateway · fastn-aiOperating manual for the fastn gateway - clear its required first read, pick and install the right fastn skill, and keep the installed copy in sync with the published version. Use whenever a task touches a fastn connector, integration, workflow, sync, widget, automation, or any external app reached through fastn.
- ▌ Unified API · fastn-aiConfigure and use the fastn Unified API through the fastn Workflow MCP — a platform-global catalog of categories (crm, ecommerce, ...) with canonical entities (contact, customer, order) that execute across whichever providers each org has connected (HubSpot, Dynamics 365, BigCommerce, Cin7, ...). Covers browsing the catalog, curating it as platform_admin (categories, entities, per-connector mappings with operations/fieldMappings/enrichActions/conditions), verifying with test and query tools, the multi-provider fan-out list shape and cursors, calling fastn.unified from workflow code, attaching a unified entity to a widget (unifiedRefs/unifiedEntityIds, auto connector merge), per-provider widget config forms, and the flat config.unifiedValues shape. Use when asked to create a unified API, add a category/entity, map a connector into a unified entity, call the unified API from a workflow or widget, add a config form to a unified widget, or to debug UNIFIED_* errors, wrong fields, or empty unified data.
- ▌ Connector Builder · fastn-aiProduction knowledge base for building and debugging fastn connectors through the fastn Connector MCP. Covers REST, GraphQL, MCP-protocol, FTP/FTPS/SFTP, DB, gRPC, and AWS Lambda connectors; every auth strategy (OAuth2/OAuth1, API key, Basic/Digest, Bearer, JWT, AWS SigV4, INPUT, NO_AUTH); action input/output contracts and bodyTemplate rules; webhook configs and subscription code; plus platform bugs and provider-specific quirks from 20+ production connectors. Use whenever creating, editing, testing, or debugging a fastn connector, auth method, action, or webhook — e.g. "build a Stripe/Salesforce/HubSpot connector", "add an action to a connector", "wire up OAuth/API-key/AWS auth", "register a webhook", "the webhook won't subscribe", or "fix the inputContract/outputContract".
- ▌ Workflow Verifier · fastn-ai bundleVerify a fastn workflow, trigger, widget, or whole use case actually works — end to end, with runtime evidence — through the fastn Workflow MCP. Runs the attached test-case suite and asserts each pass condition, fires every bound trigger and correlates the fire to a real execution (scheduler run-now, synthetic app event, webhook POST), reads back widgets/configs/installations, diagnoses failures from execution logs and traces, self-heals what it can, and always ends with a human-readable Markdown VERIFICATION REPORT (verdict, what's running, data parity, failures, blockers, coverage, cleanup, next steps). Use when asked to verify, test, QA, or health-check an existing workflow or integration ("is this working?", "verify my sync", "why didn't my trigger fire?"), after any workflow/trigger/widget/config change, and as the mandatory VERIFY phase the integration-builder skill runs after every build or update.
- ▌ Integration Builder · fastn-ai bundlePlan, map, build, and verify fastn integrations and workflows through the fastn Workflow MCP, in four phases — PLAN (discover connectors and entities, recommend a plan), MAP (probe fields, propose mappings and filters, approve, save the config), BUILD (workflows that read that config at runtime so edits need no code, test live, bind triggers, end with a widget), VERIFY (fire every trigger, correlate to a real execution, self-heal, close with a human-readable Markdown verification report). Any source→target data movement — syncs, aggregations, reshapes — plans and maps first. A single-system automation carrying user-editable business rules (a filter, a threshold, a status) still maps those into an approved config; only a rule-free one builds directly. Routes to connector-builder when a connector, action, event, or connection is missing. Use to sync, integrate, connect, or migrate data between systems, or to build or modify any fastn workflow, automate on an app event, schedule a sync, or expose a webhook.