An adapter is a secure link between your Bitcheck account and another product (for example Telegram or Gmail). After you connect, Bitcheck can receive content from that product, run the same verification you get in the web app, and keep results in your history.

• Credentials are stored encrypted; you can disconnect any time.
• Each adapter has its own settings page when it needs choices from you (what to verify, where results go, and so on).
• Not everything is available in every workspace yet — the Adapters list always shows what you can turn on today.

After you sign in, open Adapters from the main navigation. You will see every integration your account can use, grouped so you can browse before you connect.

• Personal workspaceOpen Adapters
• Business workspaceOpen Adapters

New here? Create an account first — the catalog is available once you are signed in.

Pick an adapter from the list, then follow the on-screen steps. Most flows look like this: introduce what the integration does, ask you to sign in or paste a token, then drop you on that adapter's home page in Bitcheck.

• OAuth adapters (like Gmail) open a secure window from Google so you can approve access.
• Bot-style adapters (like Telegram) may give you a one-time link to finish setup inside the other app.
• If something fails mid-way, you can always close the dialog and start again — nothing is saved until the flow completes.

You can use the shared Bitcheck bot for a quick start, or connect your own bot from BotFather for a branded experience. After you connect, send files or messages to the bot, use commands like /help, and in groups you can reply to a message with /verify when your bot supports it.

• Your-own-bot installs let you tune auto-verify, where replies go, and group muting from the adapter settings page.
• If the bot cannot see every message in a group, disable privacy mode for that bot in BotFather.
• Link codes expire after a short time — open Connect again from Adapters if Telegram says the code is invalid.

Gmail connects with Google's standard permission screen so Bitcheck can work with attachments you choose to verify. Early releases focus on linking your inbox and preparing automation — some features (like always-on background review) roll out in later milestones.

• After you approve access, visit the Gmail adapter page for attachment rules and daily limits — they apply once automation is enabled.
• If Google revokes access, you will see a reconnect banner; use Reconnect and sign in again.
• You can still verify content manually from Verify or from the API while Gmail automation catches up.

Every active adapter has a detail page inside Bitcheck. Settings hold behaviour flags (what to ingest, limits, notification style). Activity lists adapter-related events such as verification requests, retries, and errors while the link is healthy.

• Disconnect stops new events from that external account; it does not wipe verifications already in your history.
• When a provider asks you to sign in again, use Reconnect from that adapter page.
• If Activity is empty right after you connect, send a sample message or file through the other product to generate the first event.

• “Reconnect required” means the remote service no longer trusts the saved token — open the adapter and finish the prompt.
• Changed your password or security settings on the external account? Reconnect from Bitcheck.
• Still stuck? Note the time of the error and contact support from your workspace help options; include which adapter and what you tried.

Adapters cover product flows we ship in the product. When you need a custom integration, use the REST API from your servers or scripts — the same verification results surface in your history regardless of the path you choose.

Read the API documentation