Skip to main content

Connect Calendars, Routing, and Shopify Flow

Use Settings → Integrations to connect mapping, calendar, routing, export, and automation tools. These integrations are enabled in the

Use Settings → Integrations to connect mapping, calendar, routing, export,
and automation tools. These integrations are enabled in the deployed
environments. Availability badges and messages in your store remain
authoritative because EasyRoutes and Shopify Flow require Pro.

Integrations page showing connection state and plan availability

Read the badge on each integration before configuring it. Not connected
describes connection state; All plans or Pro describes plan
availability. Saving an API key or credential is not complete until its
connection test succeeds.

Google Maps

Google Maps API support is available on all plans, including Advanced.

  1. Enable billing, Maps JavaScript API, and Geocoding API in Google Cloud.

  2. Paste the key under Google Maps, select Test connection, and save.

  3. Open a radius or map-based delivery area to verify the browser map as well.

  4. Ask support for the current browser-domain and server-IP restrictions before
    restricting the key. The connection test checks server geocoding only.

Calendar subscriptions (ICS)

Private ICS calendar subscriptions are available on all plans, including
Advanced.

  1. Under Calendar subscriptions (ICS), choose the past and future day range.

  2. Leave Include customer contact information off unless the calendar
    provider and everyone with access to the private URL may receive it.

  3. Create the feed, copy its private URL, and subscribe from Google Calendar,
    Apple Calendar, or Outlook.

  4. Use Regenerate URL if the URL is exposed. Existing subscriptions will
    stop updating and must be replaced.

Calendar refresh timing is controlled by the calendar provider. Use the app
dashboard for immediate operational information.

Direct Google Calendar sync

Direct one-way Google Calendar sync requires Pro. Advanced stores can use the
private ICS subscription above with Google Calendar instead.

  1. Connect the intended Google account and select a calendar.

  2. Choose delivery, pickup, or both; choose how cancellations are handled; and
    set the date window.

  3. Decide whether to include contact email and phone. This is off by default.

  4. Enable one-way sync and save, then review the last-success and error status.

Disabling sync pauses future updates but does not remove existing Google events.
The integration does not send calendar invitations.

Shipping CSV and EasyRoutes

  • Shipping CSV exports are available on all plans. Filter by delivery date,
    method, and location, then choose whether to include email or phone. One
    export supports up to 60 days, 250 orders, and 5,000 item rows.

  • EasyRoutes requires Pro and a paid EasyRoutes plan with API access. Save
    the client ID, secret key, and separate webhook secret before exporting.
    Manual exports support up to 200 unfulfilled local-delivery orders. Route
    planning and dispatch remain in EasyRoutes.

  • Pickup CSV rows do not contain a delivery address and are not ready for route
    import.

Shipping CSV export filters and limits

Shopify Flow

  1. Install Shopify Flow and create a workflow using Delivery schedule
    changed
    from RP Local Delivery Date.

  2. Add conditions and actions, then turn on the workflow.

  3. In the app, enable Shopify Flow triggers and save.

  4. Make a new test schedule change and review the workflow run in Shopify Flow.

The custom trigger requires Pro. It does not replay existing orders. Use
Shopify's built-in cancellation and fulfillment triggers for those events.

Shopify Flow integration settings

Troubleshoot integrations safely

Start with the status and error shown in Settings → Integrations. Refresh
the status before changing credentials, and change only one setting at a time.

Google Maps

  • If Test connection reports that access was denied, confirm billing,
    Geocoding API, the key value, quota, and server restrictions in Google Cloud.

  • If the test succeeds but a map does not load, open a radius or map-based
    delivery area. Browser maps use Maps JavaScript API and website restrictions,
    which the server connection test does not verify.

  • Do not remove key restrictions merely to make a test pass. Contact RP support
    for the currently approved Rose Perl domains and outbound server addresses.

  • Contact Google Cloud support for account billing, project ownership, or quota
    changes. Contact RP support when a correctly configured key tests
    successfully but the app still cannot display or use the map.

Calendar subscriptions (ICS)

  • A newly added subscription can take time to refresh because the calendar
    provider controls polling.

  • Confirm the subscribed URL is the current private URL. If Regenerate URL
    was used, replace the old subscription in every calendar client.

  • Compare the same order and date range in the app before reporting a missing
    event. Contact the calendar provider if only its refresh is delayed; contact
    RP support if the current feed URL itself omits an eligible scheduled order.

Direct Google Calendar sync

  • Select Refresh status and review Last successful batch and Sync
    needs attention
    before retrying.

  • If Google access was revoked or the connected account changed, select
    Reconnect, approve access, save the sync settings, and then use Sync
    now
    once.

  • Do not repeatedly reconnect or sync while a batch is running. The selected
    calendar cannot be changed after events have synced; contact RP support if a
    calendar migration is required.

  • Contact Google for account access or calendar permission problems. Contact RP
    support when the connection is valid but the app reports repeated sync
    failures or incorrect event content.

Shipping CSV

  • Recheck the delivery-date range, method, and location when an export is empty.

  • Reduce the date range or filters if the export reaches its documented order
    or item limits. Older Shopify orders can require extended order access.

  • Open the file as data and keep spreadsheet active content disabled. Contact
    RP support if eligible orders visible in the app are absent from a freshly
    generated export.

EasyRoutes

  • Select Check credentials, then Refresh status. Confirm the EasyRoutes
    paid plan still includes API access and that the client ID, secret key, and
    webhook secret came from EasyRoutes Settings → API.

  • If a send outcome is unknown, check EasyRoutes for imported stops before
    sending again; retrying can create duplicate operational work.

  • Manual and automatic export send local-delivery orders only. Cancelled,
    fulfilled, and pickup orders are not eligible for manual route import.

  • Contact EasyRoutes for its plan, API access, routing, or imported-stop
    behavior. Contact RP support for app connection status, filtering, saved sync
    state, or an order that the app did not send as documented.

Shopify Flow

  • Select Refresh event status, then open the workflow's run history in
    Shopify Flow. An app event marked delivered means Shopify accepted the
    trigger; it does not prove every workflow action succeeded.

  • Confirm the workflow is turned on and uses the RP Local Delivery Date
    Delivery schedule changed trigger. Existing orders are not replayed.

  • If an event outcome is unknown, inspect Flow history before repeating the
    schedule change; the app does not automatically resend that event.

  • Contact Shopify support for Flow editor or native action failures. Contact RP
    support when an eligible future schedule change is not emitted or its
    schedule fields are incorrect.

Important warnings or limitations

Private calendar URLs, API credentials, and exported customer details must be
handled as sensitive data. Share only what the destination service requires.

  • Never send API keys, access tokens, client secrets, webhook secrets, or
    private calendar URLs in screenshots, email, chat, or support tickets.

  • Send RP support the store URL, integration name, status badge, sanitized
    error text, approximate failure time with time zone, affected order number,
    and the exact action attempted.

Suggested Articles

Did this answer your question?