Requesting New Integrations
Can't find the integration you need? We're always looking to expand Launchpad's connections based on what our operators need. This guide explains how to request new integrations and what happens next.
Before you request
Check existing options
First, verify the integration doesn't already exist:
Go to Settings > Integrations
Browse all available integrations
Use the search function if available
Check categories for the type of integration you need
Consider alternatives
If a direct integration isn't available:
Zapier — connects Launchpad to 5,000+ apps with no coding
API — build custom connections with development resources
Webhooks — receive real-time data for custom solutions
See Zapier Integration or API Access Overview for details.
How to request an integration
Submit your request
Go to Settings > Integrations
Scroll to the bottom of the page
Click Request an Integration
Complete the request form:
- Service name — what you want to connect - Service website — URL of the service - Your use case — how you'd use this integration - Priority — how important this is for your business
Submit your request
What to include
The more detail you provide, the better we can assess your request:
Describe the service:
What does the service do?
Who provides it?
Is it specific to Australia or international?
Explain your use case:
How would you use this integration?
What data needs to flow between systems?
What actions should be automated?
Share your context:
How critical is this for your operations?
Are there workarounds you're currently using?
Would you pay extra for this integration?
What happens after you submit
We review your request
Our product team reviews all integration requests:
Feasibility check — does the service have an API?
Demand assessment — how many operators need this?
Value evaluation — how much does this help tourism businesses?
Resource planning — what would it take to build?
We may reach out
We might contact you to:
Understand your use case better
Clarify technical requirements
Explore interim solutions
Invite you to beta test if we build it
You'll receive updates
We'll keep you informed:
Acknowledgement of your request
Status updates as decisions are made
Notification if the integration is built
Factors that influence our decisions
Higher priority
Integrations are more likely if:
Many operators request it — popular demand
It's tourism-specific — directly helps tourism businesses
Strong API available — technically feasible
Clear use case — obvious benefit for operators
Australian relevance — particularly useful in Australia
Lower priority
Integrations may take longer if:
Niche audience — only a few operators need it
No public API — technically difficult
Alternative exists — Zapier or another integration covers it
High complexity — requires significant development
Alternative solutions while you wait
Use Zapier
If the service is available on Zapier:
Connect both Launchpad and the service to Zapier
Create Zaps to automate workflows
This often solves the immediate need
See Zapier Integration for setup.
Build with the API
If you have development resources:
Use the Launchpad API to access your data
Connect to the other service's API
Build a custom integration
See API Access Overview for details.
Use webhooks
For real-time notifications:
Set up webhooks in Launchpad
Route data to your service
Process events as they happen
See Webhook Configuration for setup.
Manual processes
Sometimes a simple workaround works:
Export data periodically
Use copy-paste for critical information
Set reminders for manual sync tasks
Not ideal, but keeps things running while you wait.
Suggesting improvements to existing integrations
Report issues
If an existing integration isn't working well:
Try troubleshooting first (see Troubleshooting Integrations)
Contact support with specific details
We'll investigate and fix issues
Request enhancements
If an integration works but could be better:
Contact support with your suggestion
Explain what additional functionality you need
Describe how it would help your business
Examples:
"Could the Xero integration sync customer notes?"
"Could Google Calendar sync include product names in event titles?"
"Could Mailchimp integration add more customer fields?"
Contributing to the roadmap
Join our community
Connect with other operators:
Share integration ideas in our community forums
Vote on other operators' suggestions
Learn about upcoming features
Participate in feedback
We regularly seek input:
Surveys about feature priorities
Beta testing for new integrations
User interviews about workflows
Let us know if you'd like to participate.
Our integration development process
When we build a new integration:
Research — understand the service and use cases
Technical assessment — evaluate API capabilities
Design — plan how the integration will work
Development — build and test the integration
Beta testing — trial with selected operators
Release — make available to all operators
Support — maintain and improve over time
This process typically takes 2-6 months depending on complexity.
Questions about integrations
Do new integrations cost extra?
Most integrations are included in your subscription. Some advanced integrations may be available on higher-tier plans. We'll communicate any costs clearly before release.
Can you build a custom integration just for me?
We focus on integrations that benefit many operators. For unique needs, consider using our API to build a custom solution, or work with a developer who can help.
What if the service I need has a poor API?
Some services have limited or no API access. We can only build integrations where the technical capability exists. In these cases, manual processes or intermediary tools like Zapier may be the only options.
How do I know when new integrations are released?
We announce new integrations through:
Email notifications
Dashboard announcements
Help article updates
Social media
Ensure your notification preferences are set to receive product updates.
Your input shapes Launchpad's future — every integration request helps us understand what tourism operators need most.