Integrations

Myra is designed to be the central "Operating System" for your business, but it doesn't live in a vacuum. Our robust integration ecosystem allows you to connect your favorite tools, ensuring data flows seamlessly across your entire stack.

Strategic Integrations

1. Calendar & Scheduling (Two-Way Sync)

Connect Google Calendar or Microsoft 365 to ensure your availability is always accurate.

• Conflict Detection: When a client looks at your Booking Page, Myra checks your personal calendar in real-time. If you have a dentist appointment on your Google Calendar, that slot is automatically hidden.
• Write-back: When a booking is made in Myra, it is instantly added to your external calendar with all the meeting details and video links.

Outlook / Microsoft 365 (Beta): This connection is available in all accounts and is labelled Beta - it is new and still being improved, so tell us if anything looks wrong. Settings → Integrations → Microsoft / Outlook → Connect Microsoft. Calendar and email are granted separately: connecting only asks for calendar access, and you can switch Email on later from the same card if you want Myra to send from that mailbox. Work, school and personal Microsoft accounts are all supported. Myra pulls your Outlook events (including recurring occurrences, shown in your workspace timezone) into the calendar so they block availability, and writes new Myra bookings back to Outlook. Cancelling a booking in Myra removes the Outlook event. Disconnecting removes the connection and its synced events. If both Google and Outlook are connected, new bookings are written to whichever you connected most recently — never to both.

Calendly (multiple accounts): You can connect more than one Calendly account to the same workspace — for example one per salesperson. Each connection can be renamed, synced on its own, and limited to specific event types (booking pages) so only the meetings you care about land in Myra. Disconnecting one Calendly account removes only that account's bookings; the others keep syncing.

2. Email (Inbound & Outbound)

Connect your professional email via Gmail, Outlook, or IMAP/SMTP.

Sending from Outlook (Beta): Myra can send your emails through your connected Microsoft account instead of an app password. Switch Email on in the Microsoft / Outlook card in Settings → Integrations and approve the send permission; sent messages appear in your Outlook Sent Items as normal. If Myra asks you to reconnect Outlook, it is because the connection has not yet been granted permission to send — reconnecting takes a few seconds and nothing else changes.

• Unified Inbox: See all your client emails inside the Myra "Conversations" tab alongside their SMS and call history.
• Send As: When you send an email from the CRM, it comes from your actual server, ensuring high deliverability and professional branding.

3. Payments (Stripe)

The Stripe integration turns Myra into a revenue generator.

• Hosted Checkout: Send a professional payment link to a client via SMS or Email.
• Card on File: Securely store payment methods for future one-click billing or recurring subscriptions.

4. Advertising & Attribution (Meta/Facebook)

Bridge the gap between "Ad Spend" and "Actual Revenue."

• Conversions API (CAPI): Send "Offline Conversions" (like a signed contract or a paid invoice) back to Facebook. This tells the Facebook algorithm exactly which ads are resulting in money, not just clicks. Each preset can:

  • Stop re-entries - turn on "Only fire each event once per contact" so a contact moving back into a stage never sends a duplicate event.
  • Choose where the value comes from - a fixed amount, the contact's opportunity value, or any custom contact field (useful for Purchase events).
  • Custom mapping - send extra Meta parameters populated from contact details or custom fields (for example content_name from custom.plan_name), or fixed text.

• Lead Ads: Automatically pull leads from Facebook Lead Forms directly into your Myra pipelines without using third-party tools like Zapier.

Communication Infrastructure

Phone & SMS

Myra includes managed voice and text infrastructure.

• Global Reach: Provision local numbers in 100+ countries.
• Reliability: Benefit from enterprise-grade routing.
• A2P 10DLC Compliance: We handle the complex registration process for US SMS regulations (10DLC) so your messages actually get delivered.

Team Notifications

Push CRM events (new leads, bookings, deals won) into the tools your team already lives in via incoming webhooks:

• Slack, Discord

Forms & No-Code Automation

• Typeform: Native webhook endpoint with HMAC verification and custom field mapping. Mapping targets include standard contact fields and any custom contact fields configured for the workspace.
• Zapier, Make, n8n, and generic webhooks to connect to 5,000+ other apps.

Migrations

Migrations are a business-level activity and are run from Business → Migrations, not from a client account. GoHighLevel and Close are both supported (both labelled Beta), alongside CSV import with custom field mapping. There is no GoHighLevel card in client accounts.

Managing Your Connections

All integrations are managed from Settings → Integrations.

• Status Monitoring: See at a glance which connections are active and which may need "Re-authorization" (e.g., if you changed your Google password).
• Per-User Settings: Some integrations (like Personal Calendars) are connected by individual team members, while others (like Stripe) are "Workspace Wide" and managed by admins.

Custom Integrations

If we don't have a native "one-click" integration for a tool you use, you have three powerful options:

1. Incoming Webhooks: Trigger Myra workflows from any external system that can send a POST request.
2. REST API: Build a custom bridge. Our API allows you to read and write any data in your workspace.
3. Zapier / Make: Connect Myra to 5,000+ other apps via our official connectors on these "no-code" automation platforms.

Security of Your Data

We take the security of your third-party accounts seriously:

• OAuth 2.0: We use the industry-standard OAuth protocol. This means you never give Myra your Google or Microsoft passwords; you only grant us specific "Permissions" which you can revoke at any time from your Google/Microsoft account settings.
• Token Encryption: All integration "Access Tokens" are stored using multi-layer encryption.
• Minimum Scoping: We only request the minimum permissions necessary to perform the integration (e.g., we ask for "Read/Write Calendar" but not "Read All Emails" unless you specifically connect the Inbox).

FAQs

Does it cost extra to use integrations? Myra does not charge an "Integration Fee." However, some services like payments, calls, SMS, and number rental can have usage-based fees.

How often does the data sync? Most integrations (Google, Stripe, Webhooks) are "Real-Time." Data is transferred within seconds of the event occurring.

Checking your pixel credentials

When you save a Conversions API preset (or press Test connection), Myra sends an isolated test event to that exact Pixel ID using Meta's Test Events mode. This proves the token can send to the selected pixel without adding anything to live conversion reporting:

• Validation passed - Meta accepted the test event for this pixel, and Myra shows when it was checked.
• Pixel permission failed - Myra names the pixel and directs you to assign the system user behind the token in Meta Business Settings.
• Token failed - the token is invalid or expired and must be regenerated.
• Never validated - the preset has not yet completed a successful check.

Preset badges reflect what is actually happening. A preset whose recent events are being rejected shows a red Not connected - Meta is rejecting events badge with the latest error, and invalid credentials show Credentials invalid - so a broken pixel never looks healthy. The same warning appears on the Conversions API tile in Integrations.

Conversions API status

Settings → Conversions API opens with a Conversions API status panel for the selected client: events sent to Meta in the last 7 days and how many were accepted versus rejected. Accepted is worked out from Meta's actual response, so healthy setups are never reported as broken.

Three tabs sit underneath:

• Failed events — every rejection with the contact's name, timestamp, Meta's own error message, and a Retry button. Retry all failed resends up to 50 at once.
• All events — the full 7-day list with contact names and per-row retry.
• Contacts — your most recent contacts with their tracking state (Sent, Failed, or Never attempted) and a Send to Meta action to send a Lead, Schedule, or CompleteRegistration event manually.

A retry reuses the event's original event ID, so Meta deduplicates it and a conversion can never be double-counted. Manual sends are limited to a fair-use rate per workspace and only ever touch the client you are viewing.

If every event in the window was rejected, the panel shows a red warning that conversion tracking is not reaching Meta — campaigns are optimising without conversion data — along with what to check (a wrong pixel ID versus a token that was not generated for that dataset). You will also receive an integration alert email (at most one per pixel per day) for any rejection, not just expired access tokens.