Skip to main content
Coming Soon: Extensions are not currently available. This feature is under development and will be released soon.

​
Extensions Overview

Extensions (built on the valext protocol) connect Valmi Value to external systems like payment processors, accounting software, CRMs, and other business tools.
Note: The extension system is currently under development. The information below is a preview of what will be available.

​
Available Extensions

All extensions are currently in development and will be available soon.

​
Payment Processors

  • Stripe Extension: Process payments, handle subscriptions, manage customers [Coming Soon]
  • PayPal Extension: Accept PayPal payments [Coming Soon]
  • Other Processors: Square, Braintree, etc. [Coming Soon]

​
Accounting Systems

  • QuickBooks Extension: Sync invoices and payments to QuickBooks [Coming Soon]
  • Xero Extension: Sync to Xero accounting [Coming Soon]
  • NetSuite Extension: Enterprise ERP integration [Coming Soon]

​
CRM Systems

  • HubSpot Extension: Sync customer data and usage to HubSpot [Coming Soon]
  • Salesforce Extension: Integrate with Salesforce CRM [Coming Soon]

​
Other Systems

  • Slack Extension: Send notifications to Slack [Coming Soon]
  • Email Extension: Send custom email notifications [Coming Soon]
  • Custom Extensions: Build your own extensions [Coming Soon]

​
What Extensions Do

Extensions enable:
  • Payment Processing: Automatically charge customers when invoices are generated
  • Accounting Sync: Keep your books in sync automatically
  • CRM Integration: Update customer records with usage and billing data
  • Notifications: Alert your team about important events
  • Custom Workflows: Build custom integrations for your needs

​
How Extensions Work

Extensions are event-driven:
  1. Event Occurs: Something happens in Valmi Value (invoice created, payment received, etc.)
  2. Extension Triggered: The extension receives the event
  3. Action Taken: Extension performs an action (charge customer, update CRM, send notification)
  4. Result Recorded: Extension reports success or failure

​
Extension Architecture

Extensions support bidirectional data flow:

​
Outbound Flow (Valmi Value → External System)

Valmi Value → Event → valext Extension → External System
                ↓
         Response/Status

​
Inbound Flow (External System → Valmi Value)

Extensions can also work as ingestion into Valmi Value through webhooks: 
External System → Webhook → valext Extension → Valmi Value
                                    ↓
                            Response/Status
Extensions run as separate services that:
  • Subscribe to Valmi Value events (outbound)
  • Receive webhooks from external systems (inbound)
  • Transform data to match external system formats
  • Call external system APIs
  • Handle errors and retries
  • Report status back to Valmi Value