Connecting integrations (Shopify, HubSpot, Linear, and more)

Gruvi does not know what is in your Shopify store or your issue tracker until you let it look. A connection is that permission.

What a connection is

A link between Gruvi and another system you use, which skills then act through, from refunds in Stripe to orders in Shopify.

The connection on its own does nothing. It is what a skill needs to work, in the same way a knowledge source is what Chloe needs to answer.

What connections are for

Every skill in the store names what it works with, shown on its card and on its page.

Shopify

Orders, delivery status, refunds. What most e-commerce skills read from.

HubSpot

Customer history and CRM records, so replies land in context.

Linear

Issue tracking. Bug reports and feature requests become tasks.

Others

Stripe, Slack, calendar tools and more, with the list growing.

A skill without its tool connected cannot do its job, which is why connecting usually comes first.

How to connect a tool

1. 1Go to Skills, then Your skills.
2. 2Scroll to Connect your tools at the bottom.
3. 3Click Connect.
4. 4Pick the tool and sign in to it when asked.
5. 5Grant the access it requests.

You will need permission in that system, not only in Gruvi. Connecting a company Shopify store or Linear workspace generally needs an administrator there, so it is worth checking who that is before you start.

Finding skills for what you already have

The store has two controls built for exactly this.

Works with what you have

A toggle that hides every skill needing a tool you have not connected. The quickest way to see what is actually available to you today.

Connections used

A filter for browsing by tool, when you want to see everything a particular system can do.

What to check before connecting

• Who owns the account. If it is not you, involve them before granting access rather than after.
• What the skill will read. A connection is not limited to one skill; assume anything you connect may be read by the skills you install.
• Whether it can write. A connection used by an action skill can change things in that system. That is the point, and it is also the risk.
• Whether you need it yet. An unused connection is access granted for no benefit. Connect when a skill needs it.

If a skill needs something you do not have

You can still read its page and see exactly what it would do, which is often useful when deciding whether a tool is worth adopting.

What you cannot do is publish it. Rather than connecting a system solely to try a skill, rehearse it first. The rehearsal shows how the conversation would go, and that is usually enough to tell whether it is worth the setup. ---