Connectors & Integrations

Connectors & Integrations Reference

Unified abstractions, schema-driven wiring, cloud file storage backends, seamless provider switching, and zero-drop platform fallback for enterprise ASP.NET Core applications.

ProjectHelm connects generated ASP.NET Core applications to authentication providers, payment gateways, messaging networks, and cloud directories. Unlike traditional low-code sandboxes where developers manually configure fragile plugin webs, ProjectHelm treats connectors as first-class architectural primitives driven strictly by the application's declarative schema and business rules.

Schema & AI-Decided Wiring

Users never manually guess which connectors their app needs. When an application specifies Single Sign-On, payment checkout, or transactional dispatch, the AI automatically wires the appropriate connector into the project's metadata.

Strict Equivalent Swapping

Switching between providers is allowed only when both connectors fulfill the exact same job (e.g. Zoho SMTP ↔ SendGrid, Stripe ↔ Razorpay). All configured static and dynamic recipient bindings transfer losslessly.

Zero Silent Failures (Platform Fallback)

If no third-party email provider is configured or credentials expire, the application does not drop notifications or crash. All outgoing verification codes and workflow alerts automatically route through ProjectHelm's built-in mailer.

Decoupled Workflows & Automation

Event-driven pipelines (triggered on record create/update or button click) and scheduled background automation jobs (timers, intervals, sweeps) are organized into dedicated runtime views with full step introspection.

Modal Management Architecture

Inside every application workspace, the Manage Your App modal is structured into four distinct views designed for clarity and operational isolation:

Section Role & Visibility Metadata Displayed
Used Connectors Shows active integrations wired into the app's schema. Default view when connectors are present. AI UsageLabel (e.g. Customer Order Receipts), Binding mode (Static vs Dynamic), entity property mapping, and credentials status.
Workflows Event-driven pipelines executed on data mutations or UI actions. Trigger kind (EntityEvent, Button), trigger entity, conditions, and sequential execution pipeline steps.
Automation Jobs Background worker routines running on timers or schedules. Cadence (Schedule, ScheduleOnce, Interval), schedule times, UTC execution sweeps, and scheduled worker tasks.
Available Connectors Discovery catalog consolidating all platform connectors, payment gateways, and webhooks. Search filter, category pills (Auth, Payments, Communications, Security, Directory), capability cards, and setup guides.

Supported Connectors & Capabilities

ProjectHelm provides production-tested connector primitives with verified C# code emission for .NET 10, Entity Framework Core, and ASP.NET Core Identity.

Microsoft 365 & Entra ID

microsoft-365
Unified Auth & Directory

Consolidates Microsoft Single Sign-On (OAuth2 OIDC login) with Microsoft Graph Directory Sync and writeback. A single Azure App Registration powers both customer/employee login and backend directory automation routines.

Configuration Keys
  • ClientId (Required) — Azure App Registration Application ID.
  • ClientSecret (Required) — App Registration Client Secret Value.
  • TenantId (Optional) — Specific tenant or common for multi-tenant.
  • Scope (Optional) — Graph API scopes.
Endpoints & Scaffolding
  • Redirect URI: https://<app>/signin-microsoft
  • Alternative OIDC: https://<app>/signin-oidc
  • Baseline Entities: DirectoryUser, DirectoryGroup
  • Writeback Actions: User provisioning, license checks, group syncing.

Google Sign-In

google-signin
OAuth 2.0 Social Login

Seamless one-click authentication allowing users to sign up and sign in using Google Accounts with standard OpenID Connect tokens.

Configuration Keys
  • ClientId (Required) — Google Cloud Console OAuth 2.0 Client ID.
  • ClientSecret (Required) — OAuth 2.0 Client Secret.
Endpoints
  • Authorized Redirect URI: https://<app>/signin-google

Zoho & Custom SMTP Email

zoho-smtp
SMTP Relay ↔ SendGrid Swappable

Dispatches transactional notifications, auth verification codes, password resets, and workflow alert emails via Zoho Mail (smtppro.zoho.com / smtppro.zoho.in), Office 365, Gmail, or private mail gateways.

Configuration Keys
  • Host (Required) — SMTP host address.
  • Port (Required) — 587 (TLS/STARTTLS) or 465 (SSL).
  • Username & Password (Required) — Auth credentials / App password.
  • SenderEmail (Required) & SenderName (Optional).
  • EnableSsl (Optional, default true).
Binding Capabilities & Fallback
  • Static Binding: Fixed system recipient address (e.g. alerts@company.com).
  • Dynamic Binding: Entity model property (e.g. Order.CustomerEmail).
  • Fallback: Zero-drop built-in platform mailer if credentials are absent.

SendGrid Cloud Email

sendgrid
Cloud API ↔ Zoho SMTP Swappable

Sends high-throughput transactional emails using Twilio SendGrid's REST API. Shares the identical IEmailSender interface with Zoho SMTP.

Configuration Keys
  • ApiKey (Required) — SendGrid API Key starting with SG..
  • SenderEmail (Required) — Verified sender email address.
  • SenderName (Optional) — Friendly sender display name.
Seamless Provider Replacement
  • Swapping between Zoho SMTP and SendGrid automatically preserves all Static and Dynamic recipient mappings.
  • Replaces SMTP credentials with API Key seamlessly without touching business logic or view code.

Razorpay Payments

razorpay-checkout
UPI, Cards & Netbanking ↔ Stripe Swappable

Accepts domestic and international payments in Indian Rupees (INR) across UPI (Google Pay, PhonePe, Paytm), credit/debit cards, and 50+ netbanking institutions.

Configuration Keys
  • KeyId (Required) — Razorpay API Key ID (e.g. rzp_test_... / rzp_live_...).
  • KeySecret (Required) — Razorpay Key Secret.
  • WebhookSecret (Optional) — Webhook signature verification secret.
Webhook Verification Endpoint
  • Webhook URL: https://<app>/razorpay/webhook
  • Event Listened: payment.captured
  • Ensures orders are safely marked paid even if the customer closes their browser tab prematurely.

Stripe Payments

stripe-checkout
Global Checkout ↔ Razorpay Swappable

Accepts credit/debit cards, Apple Pay, Google Pay, and regional payment methods worldwide in 135+ currencies.

Configuration Keys
  • PublishableKey (Required) — Stripe Publishable Key (pk_...).
  • SecretKey (Required) — Stripe Secret Key (sk_...).
  • WebhookSecret (Optional) — Webhook signing secret (whsec_...).
Webhook Verification Endpoint
  • Webhook URL: https://<app>/stripe/webhook
  • Event Listened: checkout.session.completed
  • Cryptographically verifies payloads using the Stripe official SDK.

Telegram Bot

telegram-bot
Interactive Bot & Broadcast

Connects a Telegram Bot to collect active subscribers (via /start), send automated broadcast campaigns, and trigger event-driven workflows directly from chat messages.

Configuration Keys
  • BotToken (Required) — Obtained from @BotFather on Telegram.
  • WebhookSecret (Optional) — Derived automatically if omitted.
Auto-Registered Webhook & Entities
  • Webhook URL: https://<app>/telegram/webhook (registered automatically on app publish).
  • Scaffolded Entities: TelegramSubscriber, Campaign, CampaignDelivery.

Google reCAPTCHA v2

google-recaptcha
Abuse Protection

Protects public authentication forms (login, sign-up, password reset, invitation acceptance) against credential stuffing, automated bots, and distributed spam.

Configuration Keys
  • SiteKey (Required) — Google reCAPTCHA v2 "I'm not a robot" Site Key.
  • SecretKey (Required) — Server-side verification secret.
  • BypassIps (Optional) — Comma-separated IP whitelist for automated tests and CI.
Behavior & Integration
  • Injected transparently across Razor identity views.
  • Validated server-side via ASP.NET Core action filter before form handling.

Azure Storage Account

azure-storage
Azure Blob Storage Quota Bypass

Stores uploaded files and media in Microsoft Azure Blob Storage using the high-performance Azure SharedKey REST API. When enabled, all entity file/image uploads, multi-file attachments, calendar documents, and storefront photos route to your Azure Storage account, completely bypassing local container disk limits.

Configuration Keys
  • AccountName (Required) — Azure Storage account name.
  • AccountKey (Required) — Primary or secondary access key (AES-256 encrypted at rest).
  • ContainerName (Required) — Target blob container name (e.g. uploads). Auto-created if missing.
  • EndpointSuffix (Optional) — Defaults to core.windows.net (customizable for Azure Gov/China/private endpoints).
Unified FileStorage Behavior
  • Global Coverage: Used automatically for single files, multi-file collections, calendar attachments, and storefront product galleries.
  • Zero-Drop Fallback: Files uploaded before enabling cloud storage remain seamlessly accessible and downloadable from local disk.
  • Disk Quota Bypassed: External cloud uploads are not constrained by the container's 50 MB local volume cap.

Amazon S3

amazon-s3
AWS S3 SigV4 Quota Bypass

Connects directly to Amazon Simple Storage Service (S3) or any custom S3-compatible object storage. Uses clean, native AWS Signature Version 4 (SigV4) REST authentication with zero heavy third-party NuGet dependencies.

Configuration Keys
  • BucketName (Required) — AWS S3 bucket name.
  • Region (Required) — AWS region (e.g. us-east-1, eu-west-1, ap-south-1).
  • AccessKeyId (Required) — IAM Access Key ID.
  • SecretAccessKey (Required) — IAM Secret Access Key.
  • ServiceUrl (Optional) — Custom endpoint URL for MinIO, LocalStack, or private S3 clouds.
Unified FileStorage Behavior
  • Global Coverage: Used automatically across all file and image uploads in your application.
  • Fast Container Starts: Zero SDK bloat keeps container compilation and cold-start times sub-second.
  • Disk Quota Bypassed: Uploaded bytes stream directly to S3 without consuming local container disk storage.

Google Cloud Storage

google-cloud-storage
GCS Interoperability Quota Bypass

Stores uploaded files and media in Google Cloud Storage (GCS) buckets using Google Cloud's official S3 Interoperability HMAC protocol. Offers enterprise Google Cloud durability with zero extra client library dependencies.

Configuration Keys
  • BucketName (Required) — Google Cloud Storage bucket name.
  • AccessKey (Required) — HMAC Access Key generated under GCS > Settings > Interoperability.
  • SecretKey (Required) — Matching HMAC Secret Key.
  • Region (Optional) — Bucket location (defaults to auto).
Unified FileStorage Behavior
  • Global Coverage: Powers all entity files, images, attachments, and storefront product photos.
  • Zero Configuration Drift: Pre-authenticated SigV4 requests route directly to storage.googleapis.com.
  • Disk Quota Bypassed: Local 50 MB volume quota is not consumed by uploads.

Cloudflare R2

cloudflare-r2
Zero Egress Fees Quota Bypass

Stores files and photos in Cloudflare R2 object storage with zero egress bandwidth charges. Provides full S3 compatibility with edge-accelerated asset downloads and optional custom domain mapping.

Configuration Keys
  • AccountId (Required) — Cloudflare Account ID from dashboard overview.
  • BucketName (Required) — Cloudflare R2 bucket name.
  • AccessKeyId (Required) — R2 API Token Access Key ID.
  • SecretAccessKey (Required) — Matching R2 API Token Secret Access Key.
  • PublicUrl (Optional) — Optional custom CDN domain or r2.dev URL for direct edge asset distribution.
Unified FileStorage Behavior
  • Global Coverage: Automatically handles file saves and downloads for all entity properties, attachments, and storefront catalog images.
  • Cost Optimization: Zero data egress fees make R2 ideal for high-bandwidth media portfolios, documents, and online shops.
  • Disk Quota Bypassed: Storage scales infinitely in Cloudflare R2 without impacting container hosting quota.

Modular Capability Architecture (Lego Blocks)

ProjectHelm features an invisible modular capability engine (ProjectHelm.Modules). Capabilities like product hierarchies, online commerce, and billing operate as independent, lightweight Lego blocks that assemble additively in topological sequence before runtime code generation begins.

๐Ÿ“ฆ

Universal Product Module (product)

Universal catalog foundation with hierarchical categories and temporal pricing
Order: 10 • Foundation

Provides generic inventory primitives compatible with physical goods, digital assets, and bookable rentals. Features self-referencing category trees (up to 4–5 levels deep), multi-currency temporal pricing schedules, and stock availability metrics.

๐Ÿ›’

Storefront Commerce Module (storefront)

Minimalist buyer identity, checkout pipelines, and order transactions
Order: 50 • Depends on: product

Extends the catalog with buyer contact profiles (Customer), transactional order headers (Order), and line item snapshots (OrderItem). Seeds public catalog browsing (/shop) and checkout workflows with zero unnecessary bloat.

๐Ÿงพ

Invoicing & Billing Module (invoice)

Commercial billing documents, tax breakdowns, and payment reconciliation
Order: 100 • Depends on: product

Scaffolds billing documents (Invoice), multi-rate tax breakdowns (InvoiceItem), and payment tracking (PaymentReceipt). Seamlessly correlates with storefront orders or standalone customer invoices with printable invoice templates and payment recording workflows.

๐Ÿ“…

Appointments & Scheduling Module (booking)

Client bookings, staff availability, service offerings, and appointment management
Order: 80 • Standalone or Linked

Defines service offerings (ServiceOffering), staff assignments (StaffMember), and customer bookings (AppointmentBooking). Provides public booking flows (/book), calendar overviews, and appointment confirmation screens.

๐Ÿ“ฆ

Inventory & Stock Control Module (inventory)

Multi-warehouse inventory, stock balances, reorder alerts, and movement ledgers
Order: 30 • Depends on: product

Provides multi-location storage facilities (Warehouse), real-time on-hand balances (StockItem), and immutable movement audit logs (StockMovement). Supports reorder thresholds, low-stock dashboards, and adjustment workflows.

Sequential Assembly & View Reset Guarantees

Additive Delta Merging Modules never destroy custom properties or relations added by developers or AI prompts. When a module is applied or re-applied, missing fields are created additively without touching existing schema definitions.
Idempotent Canonical Reset When re-applying a module, custom view overrides (MvcAppOverrides) tagged to that module are cleanly purged, resetting Razor templates to pristine defaults while keeping all database tables intact.

Zero-Trust Secrets & Security Standards

ProjectHelm applies zero-trust isolation to every connector credential:

  • Encrypted at Rest: All API keys, tokens, and client secrets are encrypted using AES-256 with tenant-scoped encryption keys prior to database persistence.
  • Scrubbed Source Code Exports: When developers export the complete solution as a Visual Studio / Rider solution (.slnx), all live secrets and passwords are completely scrubbed from appsettings.json. Developers inject local dev secrets via .NET User Secrets or environment variables.
  • Strict Network Sandboxing: Published application containers run under unprivileged Linux users with read-only root filesystems and strict memory and storage quotas.

Describe your app. Read the diff. Ship it.

The source is yours to open in Visual Studio or Rider from the first build. Sign up and see what it generates for your own idea.