LimitedImplementation, done for youLearn more

What Snapflow needs from you

Your help center's address and a demo account for your product. Nothing is installed in either.

Written by Daniel Nadasan
Updated 1 min read

On this page

Snapflow needs two things: your help center's address and a demo account for your product. There's nothing to install in your product or your help center, and no code to write.

Your help center's address

Snapflow reads your help center to find every article and the screenshots in it. Each article's text tells it what a screenshot is meant to show.

It works with Intercom, Zendesk, HubSpot and other platforms. Help center platforms has the full list.

A demo account for your product

Snapflow signs in to your product with this account to reach the screens in your articles. The account should:

  • Sign in with a username and password. Snapflow can't complete single sign-on or two-factor prompts.
  • Hold sample data, not real customers. Whatever the account can see can end up in a screenshot. The glossary explains demo accounts and sample data.
  • Have only the access your screenshots need. You decide what the account can do, and you can remove it at any time.

If your articles cover screens that only some users can see, add an account for each. See Use a demo account for each role.

What Snapflow doesn't need

  • Nothing installed in your product. No snippet, SDK or browser extension.
  • Nothing installed in your help center.
  • No developer. One is only needed if you want screenshots retaken on every deploy, which is optional.

What it won't do in your product

Snapflow never confirms a deletion, a payment, a plan change or a message to other people. It stops before the button and takes the screenshot there. Security lists everything it will and won't click.

Did this answer your question?

Still stuck?

Email daniel@usesnapflow.com and you'll hear back from Daniel, who built Snapflow.