Help Center

Install, configure, and test an integration

Move a catalog connector from installed to working.

Understand the outcome

Installing isn’t enough; finish setup and pass the connection test.

Integrations connects outside services and your own modules to Station Clipboard. The catalog has 14 connectors: six weather providers, a local news feed, Active911, PSTrax, WhenToWork, and in-house sources for Announcements, Scheduling, Time Clock, and Credits. Installed integrations feed Station Board widgets, the department calendar, the Incident Command call picker, and CAD importing in Incident Reporting. Integrations bring information in; they do not write back.

What this procedure is for

This guide focuses specifically on “Install, configure, and test an integration.” Complete it from an account with the appropriate Integrations access, verify it from the affected member or operational view, and preserve existing records rather than repurposing historical configuration.

Before you begin

Make the decision before changing the screen. Record the current configuration when the department already uses this feature, and use a test record or test account when the change can affect active members.

  • Choose the provider.
  • Get any key, token, or feed URL.
  • Name the owner of the outside account.
If a control is missing

Do not work around it from another member’s account. Confirm that Integrations is enabled, its dependencies are active, and your role grants the exact management action required for this task.

Where to work and what access you need

Start from the portal destination named in the procedure. Administrators normally need permission to view Integrations plus the specific create, edit, manage, approve, report, or all-record action used by the task. Visibility alone does not grant management access.

  • Integrations/settings/integrations
  • Integration detail/settings/integrations/:slug
  • Integration preferences/settings/integrations/preferences

Required foundation

  • Core must be enabled and correctly configured before this workflow can operate reliably.

If your department uses custom roles, test the procedure with that role—not only with a full administrator account. This confirms the people responsible for daily operations can complete the workflow without receiving unrelated access.

Complete the task

  1. Step 1Open Integrations

    Go to Settings → Integrations and open the connector.

  2. Step 2Install

    Install it.

  3. Step 3Configure

    Enter the required settings; saved secrets aren’t shown again.

  4. Step 4Test

    Run the connection test.

  5. Step 5Use it

    Add it where it’s used.

  6. Step 6Record ownership

    Note who renews the outside account.

Operational safeguards

Apply these module-level controls while completing the procedure. They prevent a technically saved configuration from becoming an operational or access problem later.

  • Control point
    Choose one provider per need and record who owns the outside account.
  • Control point
    Enter credentials only in the integration screen, never in messages.
  • Control point
    Run the connection test before building widgets on it.
  • Control point
    Confirm live data where it is used.
  • Control point
    Plan credential rotation.
  • Control point
    Remove or disable connectors you no longer use.

Verify the result

Do not consider the setup complete merely because the save action succeeded. Confirm the behavior from the user-facing or operational view, then retain evidence of the test when department policy requires it.

  • Status shows installed with a recent test.
  • Data appears where it is used.
  • No last error is shown.

If any verification fails, return to the source configuration and correct it there. Do not edit a report or downstream record to conceal an incorrect setup.

Troubleshooting

Installed but no data

Finish setup, test, and select the source.

Authentication fails

Check the key or token with the provider.

In-house source missing

Enable the related module.

Related Integrations capabilities

This task sits inside a larger module workflow. These related capabilities may affect the result or provide the next administrative step:

  • Weather: National Weather Service and Open-Meteo (no key), plus OpenWeatherMap, WeatherAPI.com, Tomorrow.io, and AccuWeather (your key)
  • Local News Feed for any RSS or Atom feed
  • Active911 recent CAD alerts for Station Board, the Incident Command picker, and Incident Reporting CAD import
  • PSTrax checks due, open alerts, fleet status, and notices for station displays
  • WhenToWork hourly, read-only sync of shifts onto the department calendar
  • In-house sources for Announcements, Scheduling, Time Clock, and Credits when those modules are on
  • Keys and tokens stored server-side; the screen shows only whether one is saved
  • Last tested time and last error for every installed connector

Use the module hub to open the dedicated procedure associated with any capability listed here.

Connected modules and downstream effects

A change here can alter what members see, what data appears in reports, or how another module completes its workflow. Review the connected areas below before making a department-wide change.

  • Station BoardStation TV boards with live widgets, rotating slides, and protected launch links.
  • Incident ReportingGuided NERIS reports, CAD-started drafts, auditor review, and transmission.
  • Incident CommandA full-screen Command Portal with checklists, PAR, units, map, and timeline.

After deployment, test one complete workflow from the originating module through every connected destination your department uses. Document the final configuration so another administrator can audit or reproduce it later.

Continue in Integrations

Return to the Integrations module guide for connected workflows, dependencies, portal destinations, and additional procedures.

Was this article helpful?

Your feedback helps us make these guides more useful.

Related guides