Connectors & Integrations Reference
Unified abstractions, schema-driven wiring, 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.
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.
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.
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.
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-365Consolidates 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.
ClientId(Required) — Azure App Registration Application ID.ClientSecret(Required) — App Registration Client Secret Value.TenantId(Optional) — Specific tenant orcommonfor multi-tenant.Scope(Optional) — Graph API scopes.
- 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-signinSeamless one-click authentication allowing users to sign up and sign in using Google Accounts with standard OpenID Connect tokens.
ClientId(Required) — Google Cloud Console OAuth 2.0 Client ID.ClientSecret(Required) — OAuth 2.0 Client Secret.
- Authorized Redirect URI:
https://<app>/signin-google
Zoho & Custom SMTP Email
zoho-smtp
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.
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).
- 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
Sends high-throughput transactional emails using Twilio SendGrid's REST API. Shares the identical IEmailSender interface with Zoho SMTP.
ApiKey(Required) — SendGrid API Key starting withSG..SenderEmail(Required) — Verified sender email address.SenderName(Optional) — Friendly sender display name.
- 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-checkoutAccepts domestic and international payments in Indian Rupees (INR) across UPI (Google Pay, PhonePe, Paytm), credit/debit cards, and 50+ netbanking institutions.
KeyId(Required) — Razorpay API Key ID (e.g.rzp_test_.../rzp_live_...).KeySecret(Required) — Razorpay Key Secret.WebhookSecret(Optional) — Webhook signature verification secret.
- 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-checkoutAccepts credit/debit cards, Apple Pay, Google Pay, and regional payment methods worldwide in 135+ currencies.
PublishableKey(Required) — Stripe Publishable Key (pk_...).SecretKey(Required) — Stripe Secret Key (sk_...).WebhookSecret(Optional) — Webhook signing secret (whsec_...).
- Webhook URL:
https://<app>/stripe/webhook - Event Listened:
checkout.session.completed - Cryptographically verifies payloads using the Stripe official SDK.
Telegram Bot
telegram-bot
Connects a Telegram Bot to collect active subscribers (via /start), send automated broadcast campaigns, and trigger event-driven workflows directly from chat messages.
BotToken(Required) — Obtained from@BotFatheron Telegram.WebhookSecret(Optional) — Derived automatically if omitted.
- Webhook URL:
https://<app>/telegram/webhook(registered automatically on app publish). - Scaffolded Entities:
TelegramSubscriber,Campaign,CampaignDelivery.
Google reCAPTCHA v2
google-recaptchaProtects public authentication forms (login, sign-up, password reset, invitation acceptance) against credential stuffing, automated bots, and distributed spam.
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.
- Injected transparently across Razor identity views.
- Validated server-side via ASP.NET Core action filter before form handling.
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 fromappsettings.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.