Simple FileMaker payload
Build a structured payload in FileMaker, pass it to the integration script, and receive the compose URL needed to continue the workflow.
Built for FileMaker developers dealing with New Outlook
Reliable email compose from FileMaker, without fighting New Outlook.
DBMailBridge helps FileMaker solutions hand off prepared email content to a modern Outlook compose experience. Your FileMaker script builds the message payload, passes it to DBMailBridge, and receives a compose link that opens the prepared message for the user.
Developer-friendly integration
Customer admin portal
Review-before-send workflow
Time-limited secure links
Rich HTML email bodies
Non-blocking FileMaker scripts
Replace fragile workarounds.
Keep your FileMaker scripts focused on building the payload. DBMailBridge handles the bridge into Outlook compose, including the add-in workflow your users need.
The problem is not your FileMaker solution.
Many mature FileMaker systems rely on email compose workflows that used to feel predictable. New Outlook changes that equation, especially where local mail client handoff, attachments and controlled compose behaviour are involved.
DBMailBridge gives developers a practical way to preserve the business workflow their clients already depend on, without rebuilding the entire email process from scratch.
1
Existing Send Mail workflows can become unreliable
Systems that worked for years can behave differently once users move to New Outlook or operate across mixed Outlook environments.
2
Attachments and formatting still matter
Clients expect the final composed message to include the right recipients, subject, body content and files, with a chance to review before sending.
3
FileMaker scripts should not have to wait on the email window
Traditional Send Mail workflows can leave the FileMaker script waiting until the user has dealt with the email. DBMailBridge is designed so your script can hand off the compose request and continue the workflow.
4
Supportable beats improvised
A proper bridge gives developers a repeatable path that is easier to document, deploy and support across customer environments.
Designed around the way FileMaker developers actually work.
Build the same data you already know: recipients, subject, body, format and attachments. Your script passes that payload to DBMailBridge and receives a compose link that Outlook users can open and review.
Modern Outlook handoff
Users get a familiar compose step where they can review and adjust the prepared message before sending.
Customer-controlled setup
Each customer has an account area for credentials, usage visibility, add-in downloads and user attribution.
Fast proof of concept
Test the workflow with a real FileMaker file before committing to a wider customer rollout.
Secure message handoff
Email content is passed through a controlled bridge using time-limited links that are available only to the nominated email account.
Built for rollout
Deploy the Outlook add-in centrally through Microsoft 365 admin, or let individual users add it directly where that suits the customer environment.
Rich HTML email output
Build email bodies with full rich HTML capability instead of being boxed into plain, fragile or client-dependent formatting behaviour.
Keep FileMaker moving
Avoid the blocking behaviour of FileMaker's Send Mail script step, where script execution can pause until the user has dealt with the email compose window.
A clear workflow from FileMaker to Outlook compose.
The FileMaker developer controls the payload. DBMailBridge provides the secure handoff and Outlook add-in workflow that completes the compose experience.
Create an account
Set up the customer account, retrieve the Customer UID and API key, and keep those values in the FileMaker solution.
Deploy the Outlook add-in
Install the add-in through the Microsoft 365 admin centre for all users, or allow individual users to add it directly in Outlook.
Build and pass the payload
Your FileMaker script creates the payload with recipients, subject, body, formatting and attachments, then passes it to the integration script.
Open compose
DBMailBridge returns the compose link, and the Outlook add-in completes the prepared message workflow for user review while FileMaker is free to continue its own script logic.
Built with Security In Mind.
DBMailBridge is designed for a temporary compose handoff, not long-term storage of customer email content. The service keeps the information needed to prepare the message only for the period required to complete the Outlook compose workflow.
Time-limited links
Compose links expire for security purposes, eliminating the chance of an old link being opened later by mistake or data leakage to cyber attacks.
Available only to the nominated mailbox
The Outlook add-in workflow is tied to the intended email account, so prepared content is not able to be opened by unrelated users.
Automatic data cleanup
Our system removes message body content, recipients and attachment data after the link has expired, while keeping a lightweight audit record showing the subject and which account requested the compose link.
No mailbox access required
DBMailBridge does not read, scan or send from a user’s mailbox. Your user’s Microsoft 365 account stays under your organisation’s control while the add-in completes the prepared email.
Secure Transmission
All network transmission is protected by SSL and Digitally Signed payloads ensuring privacy and data integrity. The Email itself continues to be sent by Outlook through existing servers. No DNS changes required.
Need more options or control?
Ask us about options for self-hosting, ensuring that your data remains 100% within your control.
Practical audit trail, less retained content.
History is retained only for usage reporting and support while storing message bodies, recipient lists and attachments only as long as required.
Simple pricing for evaluation, rollout and support.
Start with a limited evaluation account, then move to a yearly plan when the workflow is ready for production use. Higher-volume or specialised integrations can be discussed before rollout.
Free / Evaluation
Evaluation tier
$0 AUD
For evaluation, testing and initial integration work.
- Includes 150 email links
- More evaluation links available on request
- Business Hours Email support for initial integration
- Suitable for proof-of-concept testing
Standard
Standard tier
$250 AUD / year
For production FileMaker solutions with predictable monthly usage.
- 2,000 email compose links per month
- 50 users
- More links available upon request
- Priority email support for integration and maintenance
Premium
Premium tier
$400 AUD / year
For customers who want the simplest production usage model.
- Unlimited email links
- 200 Users
- Priority email support
- Phone and remote integration/debugging support during AU business hours, (up to 3 hours) included
Need help adapting this to a specific FileMaker solution?
Custom consulting, customisation and integration support is available for payload design, script implementation, add-in deployment, debugging and customer-specific workflow requirements.
Contact Us
System requirements and compatibility.
DBMailBridge is designed for modern FileMaker solutions and Microsoft 365 Outlook environments where an Outlook add-in can be installed by an administrator or by individual users.
| Area | Requirement | Notes |
|---|---|---|
| FileMaker | FileMaker Pro 16 or later recommended | The integration expects native JSON functions and CryptAuthCode support, both introduced in FileMaker Pro 16. |
| Outlook Classic | Supported where Office add-ins are available | Suitable for organisations that still use Classic Outlook alongside newer Outlook clients. |
| New Outlook | Supported through the Outlook add-in workflow | Designed to provide a practical compose path for environments moving away from older desktop mail handoff behaviour. |
| Outlook on the web | Supported through the Outlook add-in workflow | Useful for users who work primarily in the browser or across multiple devices. |
| Microsoft 365 | Microsoft 365 email account with permission to load an add-in | The add-in can be deployed centrally through the Microsoft 365 admin centre, or installed directly by individual users where allowed by policy. |
| Developer work | FileMaker developer builds the message payload | Your FileMaker script prepares recipients, subject, body, formatting and attachments, then passes the payload to the DBMailBridge script. |
Frequently asked questions.
Answers to the practical questions FileMaker developers and customer administrators usually ask before testing the workflow.
Why is there a yearly cost?
DBMailBridge is a hosted service that needs reliable cloud infrastructure, secure link handling, email verification, usage tracking, maintenance and support. The yearly fee helps cover hosting and upkeep so the bridge remains available when your FileMaker users need to create Outlook messages.
Isn't this just creating an email link?
No. The visible result to FileMaker is a compose link, but DBMailBridge also manages the secure temporary handoff and insertion of subject, body content (Text or HTML), recipients and attachments into Outlook ready to review and send.
Can the email body use rich HTML?
Yes. The FileMaker solution can build and submit a rich HTML body as part of the payload, allowing more polished customer-facing messages than many traditional handoff approaches.
Will FileMaker wait for the user to finish the email?
No. The goal is to avoid the blocking behaviour often seen with FileMaker's Send Mail script step. Once the payload has been submitted and the compose link is returned, your FileMaker script can continue with its own workflow.
Who builds the FileMaker script?
Your FileMaker developer builds the payload from existing business logic in your FileMaker solution. DBMailBridge provides the receiving endpoint, account credentials, Outlook add-in workflow and supporting documentation.
If you require assistance with adapting the scripts for your solution, we are able to offer customised consulting to make sure your solution works as smoothly as possible.
Do all Outlook users need the add-in?
Users who will use DBMailBridge need access to the Outlook add-in in their Microsoft 365 account. It can be deployed centrally through the Microsoft 365 admin centre or installed by individual users if your organisation allows that.
What happens to the message content after use?
Links are designed to expire shortly after generation, preventing accidental data leakage. Your confidential content is removed from our servers after expiration.
Can this be adapted outside FileMaker?
Yes. Our first focus is FileMaker because that is where the New Outlook handoff problem is most obvious, but the same general approach can be adapted for other database systems that can build and submit a structured message payload.
For FileMaker teams who need a practical path forward.
DBMailBridge is intended for developers, consultants and organisations that rely on FileMaker-based business workflows and need a reliable way to prepare email compose actions for Outlook users. It is especially useful where the developer wants to preserve the existing FileMaker-controlled business logic while improving the Outlook handoff.
Not using FileMaker but have another Database that needs to talk to New Outlook?. Send us an enquiry as this solution is adaptable to non FileMaker platforms as well!
FileMaker is a trademark of Claris International Inc. DBMailBridge is an independent product and is not affiliated with, endorsed by, or sponsored by Claris International Inc. or Apple Inc.
Have a question before creating an account?
Send an enquiry if you want to discuss compatibility, rollout, pricing, consulting support, self-hosting, or whether DBMailBridge can be adapted to a non-FileMaker workflow.
Integration questions
Plan upgrade enquiries
Custom consulting
Self-hosting options
Ready to test the bridge with a real FileMaker workflow?
Create a customer account, retrieve your integration credentials, download the Outlook add-in, and start testing the payload workflow from FileMaker.
Create account