Skip to content

Installing Apps

Once tools are published to the marketplace — whether by your own team or by other companies — you can install them on your agents from the Apps page. This guide covers browsing, installing, configuring, and managing marketplace apps.

Navigate to Apps in the dashboard sidebar. The page is one catalogue you scroll through, not a set of tabs:

  • A search box matches an app’s name, description, category and tags.
  • A row of filter chips narrows the list: All, one chip per app family (such as commerce or accounting), Agents for shared agent templates (see Shared Agents), Other apps, Installed, and Published by you.
  • Below that come a Your apps strip with what your company has installed, a Featured row, and one section per family.

The catalogue includes your company’s own apps, apps shared with you, and publicly listed apps.

Each card shows the app’s icon, name and a one-line summary, with a pill for Agent, New or Private where it applies, and an Install or Open button. Click a card to open its details: the version, who can see it (an app listed for everyone shows as Public), its search terms, and for an app you published, how many teams use it.

  1. Click Install

    Find the app and click Install on its card or in its details. Simple apps install in one click and are immediately available. Any member of your company can install an app.

  2. Provide required secrets, if the app declares any

    Apps that need API keys or credentials take you to their detail page first, where each declared secret has a labelled field. For example, a weather tool might need a WEATHER_API_KEY. The Install button stays disabled until every required secret has a value. These values are encrypted and stored securely — they are never visible in tool code or agent conversations.

  3. Approve any extra consent the app asks for

    Some apps request capabilities that need your explicit sign-off at install time — for example, permission to act on your connected integrations or to register fulfilment locations in your commerce platform. Review the consent panel on the detail page before confirming. See App Permissions and Grants.

  4. Connect the external account, for integration apps

    Integration apps take you to their Configure page after installing. The account itself is connected through the app: from the app’s own page (Configure shows an Open button for apps that have one), or by asking an agent to connect it, which gives you the sign-in link.

Apps at the shared trust tier are not listed in the public catalog. The publisher sends you a private share link instead. Opening the link takes you to the app’s detail page, where you can review the manifest and install it — the link itself authorises both viewing and installing for your company.

Pick the Installed chip, open an app’s details and click Configure to manage its version, secrets and agent access. Apps that ship their own pages show an Open button instead, which takes you straight to the app.

By default, installations track the latest version: when the author publishes a new version, your installation is upgraded automatically. If you need stability and want to control when updates happen, switch from Latest (auto-update) to a pinned version on the Configure page. When pinned, your installation stays on that version even when the author publishes updates, and you can move to a newer version manually when you are ready.

If a new version introduces problems, pick an earlier version from the version history on the Configure page. Only owners and admins can change an install’s version, pinned or rolled back.

Owners and admins can uninstall an app from its details. Uninstalling removes more than the tools: the app’s data, files, schedules and connections are deleted too, and it can take up to a minute. An app that keeps your records (a system of record) asks you to confirm deleting them first.

Some apps connect to an account that belongs to a person rather than to the company (Google Workspace, Xero, and the mail apps, for example). These apps use per-user connections: each member connects their own account (through the app’s own page, or by asking their agent for the sign-in link), and every tool call resolves the calling person’s own credential, so holding the tools grants access only to your own account. An install can also be limited to specific agents. Then only the people whose companion is selected, plus owners and admins, can see it.

Some apps can be installed starting from the provider rather than from Sprigr Team, for example a Shopify App Store install. The provider’s install flow hands you back to Sprigr Team, where the app is installed, the account is connected, and you land in a ready workspace and chat. Connecting an additional store or account later goes through the same in-app flow as the first.

Apps that ship their own pages are reachable at {slug}.apps.sprigr.com. From the app’s per-install page (the Open link on the Apps page) you can attach your own hostname instead: add the domain, create the CNAME record the panel shows (custom.sites.sprigr.com by default), and verification flips the domain active automatically once DNS propagates.

Disconnecting an integration without uninstalling

Section titled “Disconnecting an integration without uninstalling”

Integration apps (Shopify, Procore, simPRO, LinkedIn, Google Merchant Center, Email, and others) let you disconnect the external account while keeping the app installed, so you can reconnect a different account or pause access without losing the app’s settings. Disconnect from the app’s own settings page, or ask an agent to do it.

Several capabilities that started as built-in integrations are now delivered as marketplace apps: Google Workspace (replacing the legacy Gmail, Google Calendar, Sheets, Docs, and Drive integrations), Microsoft 365 (replacing Outlook Mail, Outlook Calendar, Microsoft Teams, and OneDrive), Gorgias, and GitHub. The retired built-ins no longer appear in the Add integration picker. The Google and Gorgias built-ins have been removed and no longer load at all, so those need the app. Existing Microsoft and GitHub built-in connections keep working until you connect the app; then the built-in stops loading and the app’s tools take over under the same tool names. The Integrations section lists which connections are built in and which are apps.

Secrets are per-installation, meaning each company that installs an app provides their own API keys and credentials. You can update secrets at any time:

  1. Click Configure on the installed app.
  2. Go to the secrets section — each secret shows whether it is set and when it was last updated.
  3. Update the values you need to change and save.

Updated secrets usually apply to the running app straight away. If the app has no running build to update, saving starts a rebuild and the new values apply when it finishes; the Configure page tells you which happened. Owners and admins change secrets on a company-wide install; a member can change them only on their own personal install.

By default an installed app is available to all agents in your company. Personal-mailbox apps are the exception: they start out scoped to the installer’s own companion, and some of them cannot be opened to all agents. Owners and admins can change an app’s agent access at any time:

  1. Click Configure on the installed app.
  2. Go to the agent access section.
  3. Switch between all agents and a specific list, or add and remove individual agents.
  4. Save.

Changes take effect immediately. Agents that lose access will no longer see the tool in their available tools list.

To build your own tools for the marketplace, see Creating Custom Tools.

To understand and manage the permissions apps hold in your organisation, see App Permissions and Grants.

For an overview of the marketplace system including trust tiers and security, see the Marketplace Overview.