Triggers are how you embed cards directly into your CRM or other SaaS apps. They use the text on the page to determine where to add the card.

You can create a trigger from the "Overview" page in the content directory, or you can create a trigger directly from a card.

We use the text directly on the page to determine where to put a trigger. So if you create a trigger "Decision Maker Bought-In" to go on your deal stage, then we'll show the selected icon (Bolt in the above image). When you click the icon, the selected card will be shown.

The "Application" field is used to determine where a card should appear. If we don't have the app that you use, you can always select the "Any" option.

Triggers will be seen on certain domains. We include some default applications to get you started, but you can customize them for any app you use.

Here's an example of a trigger in the HubSpot deal pipeline table:

By default, a trigger will appear on all pages of the selected application. But, you can actually restrict it further based on the page URL.

The Chrome Extension will take whatever you put in this and compare it against the current page's URL. It will turn * symbols into a wildcard that can match anything. You don't need to include the domain, but you can if you want.

For example, the following restrictions would allow the card to appear on the contacts page (0-1 in HubSpot), or when editing a workflow.