Choose the services your operation needs
Start with a workflow your customers or team need, then connect the provider that supports it. Keep the provider account, usage costs, and verification steps clear for whoever runs the operation.
Match the service to the outcome
| Operational need | Relevant setup guides | What to verify |
|---|---|---|
| Improve address lookup or choose a mapping provider for supported operations | Google Maps, HERE Maps, Mapbox | Representative addresses and routes in your service area |
| Send customers timely SMS messages | Twilio or Telnyx | A test notification arrives at a number you control |
| Send transactional email with your own sending setup | Mailgun | Delivery, sender name, domain, and provider logs |
| Accept customer card payments | Stripe | Onboarding, payment capability, and the payment workflow |
| Send operational messages to Slack | Slack | The intended workspace, channel, and test message |
| Use AI-powered conversational queries | Anthropic | A small test query and usage in the expected account |
| Provide audio or video through a workflow using LiveKit | LiveKit | Both participants connect and exchange media |
Choose the provider for your coverage, existing account, workflow, and usage needs. You do not need every provider in this list. For your own order-system connection, use API keys and webhooks.
Prepare the account and a small test
You need administrator access to the RouteIQ site and permission to configure the provider account. Decide who owns the account, which environment you are using, and who will respond if the integration fails.
- Check the provider's current pricing, limits, regional availability, and required setup before using it for customer work.
- Use credentials dedicated to this connection where the provider supports them. Keep test and production accounts or credentials clearly identified.
- Choose a small test you can observe: a notification to your own device, a known address, or a provider's supported payment test.
Provider charges and account requirements are separate from the RouteIQ subscription. Some workflows have platform-supported defaults; premium services can require your own provider account. Check the current coverage and pricing notes and the relevant setup guide before assuming a connection is required or included.
Connect and configure the site
- Confirm the current site, then open Settings → Integrations.
- Find the relevant provider and open its Setup guide if you need the account-side steps.
- Turn on the provider. If a connection button appears, complete that provider's authorization or onboarding flow.
- For a provider configured with credentials, wait until it shows Connected, then select Configure.
- Fill in the required Configuration fields, leave Is Active selected, and select Save.
- Return to the feature that will use it and complete any required feature settings.
Stripe has its own onboarding flow; follow its guide instead of looking for a Stripe secret-key field. Other providers have different credential and region requirements.
For example, an SMS provider supplies message delivery. You still need the relevant notification rule and channel settings, a valid recipient number, and a real test of the event that sends it.
Choose mapping operations deliberately
Mapping providers can be assigned to particular operations, such as address autocomplete, geocoding, routing, or travel-time matrices. That lets you choose a provider for a specific need without assuming it must handle every mapping feature.
Read the selected provider's guide and choose only the operations it supports. The same operation cannot be assigned to two active mapping integrations. If an operation is already assigned, review that existing provider before moving it.
Test the actual operation you changed. A successful address search does not prove routing works, and seeing a map does not prove a particular provider calculated the journey.
Verify the result customers will use
- Reopen the integration and confirm the intended site and configuration remain active.
- Run the small test you prepared through the real RouteIQ feature.
- Check the customer or operator result and the provider's activity where available.
- Repeat with representative addresses, devices, or networks before relying on the connection for normal work.
Connected means a connection record exists; it does not prove every credential or remote capability works. Sync has provider-specific behavior and is not a universal credentials test. Use the verification steps in that provider's guide.
Maintain or remove a connection
When replacing credentials, save the replacement, run the feature test, and retire the old credential after the new one works. Keep account ownership and renewal details somewhere the team can find them.
To pause use, turn off the integration and check what the affected workflow now does. To remove its saved connection, use Disconnect and read the confirmation. Review jobs, notifications, or payment work that relies on it before disconnecting.
Removing an integration in RouteIQ does not necessarily cancel the provider's account or billing. Manage the provider relationship in that provider's own account.
The card is connected but nothing happens
Check its active state, required credentials, region, feature-level settings, and recipient or test data. Then inspect the provider's response or logs.
The provider I want is not listed
Use the integrations available in the current site. For a custom connection, review the API and webhook guides or contact support about the intended workflow.