Integrations
Integration packs and setup guides for revenue machinery.
Browse setup guidance and see which integration packs you can start today. Visit the build hub to choose what you want Armalo to work on.
Stripe
In preparationNo launch date is published. Read the changelog for updates. Read the changelog
Setup guidance for subscriptions, invoices, and signed webhook fulfillment is in preparation.
Prerequisites
- A Stripe account in test mode (publishable + secret key).
- Stripe webhook endpoint URL — Armalo mints this when the workspace is provisioned.
- Whitelisted signing secret (rotated by the platform; you do not handle it directly).
Verification steps publish at launch.
Meta ads
In preparationNo launch date is published. Read the changelog for updates. Read the changelog
Setup guidance for server-side conversion events and campaign measurement is in preparation.
Prerequisites
- Meta Business account with ad account + pixel set up.
- Conversions API token with ads_management + business_manage scopes.
- Pixel ID + dataset ID captured from Events Manager.
Verification steps publish at launch.
No launch date is published. Read the changelog for updates. Read the changelog
Setup guidance for WhatsApp messaging and verified webhooks is in preparation.
Prerequisites
- Meta WhatsApp Cloud API enabled on your business number.
- Permanent access token (rotate quarterly per Meta guidance).
- WhatsApp webhook subscription fields configured (messages, message_status).
Verification steps publish at launch.
No launch date is published. Read the changelog for updates. Read the changelog
Email answering is in progress. The self-serve email pack has no published launch date.
Resend for transactional email. Inbound webhook + outbound event stream; campaign sends require approval.
Prerequisites
- A verified domain in Resend.
- API key with mail.send scope; webhook signing key.
- Region selection (EU or US) declared in the workspace config.
Verification steps publish at launch.
Build your own integration
Every integration runs through one port, with credentials held by the credential broker. Read the contract and port surfaces in the engine architecture — or the source on GitHub: catalogue-operator.ts and credential-vault.ts.