Other integrations
Use the setup model required by the integration. A bot token, webhook or service key is not the same as an OAuth app review.
Telegram bot connections
Connect a Telegram bot to a target chat
Open Telegram BotFather + your application’s Telegram connection
Workspace user with permission for the target channel/group
- Open the official BotFather in Telegram. Use
/newbotfor a new bot, or obtain the existing bot’s token if you are authorized to use it. - Add that bot to the intended test channel/group and assign the rights needed by your actual operation.
- In the application, start the Telegram channel/group connection. Enter the token in Access token.
- Select Validate token and continue. Follow the flow’s instruction to send one fresh message in the target chat so the application can detect it.
- Check the detected bot/chat identity and complete the connection. Test one deliberate message in that disposable destination.
Expected result The connection identifies the correct bot and target chat, and its test message reaches that chat.
If this does not happen Check token validity, bot membership/rights and the new target-chat message. Do not paste a different user account’s token.
Discord webhook connection
Connect a Discord channel webhook
Open Discord target channel + the application’s Discord connection form
Authorized channel administrator / workspace user
- In Discord, obtain an authorized incoming webhook for the exact channel that should receive posts. Keep its URL private.
- Open the application’s Discord connection form. In Display name, use a name such as Announcements.
- Paste that channel’s complete incoming Webhook URL in Webhook URL. This form does not ask for a bot Client ID.
- Select Connect channel. For an existing connection, the submit label is Save changes.
- Send one intended test post and check that it arrives in the selected Discord channel.
Expected result The connection is saved and the actual intended channel receives the test post.
If this does not happen If delivery goes to the wrong channel, replace the connection with that channel’s correct webhook; changing Display name does not change the webhook destination.
Mastodon and instance-specific OAuth
Connect the account’s Mastodon instance
Open Your application → Mastodon connection form
Workspace user
- Find the full HTTPS server address used by your actual Mastodon account.
- Enter it in Mastodon server URL. Use the server address, not a post URL or your profile’s @handle.
- Select Continue with Mastodon. For a reconnect, the control is Continue reconnect.
- Authorize the app at that instance and return through its callback. Check the connected account before running a test action.
Expected result The account from the intended instance is connected.
If this does not happen Check the instance URL, account and instance policy. An account on a different Mastodon server is a different authorization context.
Reddit, OK and other provider-specific apps
Use only the provider/module installed and enabled on your site. Check the source settings below for credential labels and callback paths, then check that provider’s current developer-access process before creating an app or submitting an access request. A source callback by itself is not a complete, verified setup procedure for these providers.
These are fields and default paths found in the reviewed source version. An installed module or a source default does not prove platform approval. Copy the complete URL shown by your running installation; do not paste a path by itself into a developer console.
StackPosts — Reddit / AppChannelRedditProfiles
| Setting label | Source information |
|---|---|
| Status | Use the value shown by your installation or issued for your app. |
| Client ID | Use the value shown by your installation or issued for your app. |
| Client Secret | Use the value shown by your installation or issued for your app. |
| Permissions | save,modposts,identity,edit,flair,history,modconfig,modflair,modlog,modwiki,mysubreddits,privatemessages,read,report,submit,subscribe,vote,wikiedit,wikiread (source default; review necessity and actual granted access before requesting) |
| Callback URL | /integrations/reddit/profile |
Version: 1d0944d30f606782c9abf5b878224cdd3cd09b99
Open the source definitionStackPosts — OK / AppChannelOkGroups
| Setting label | Source information |
|---|---|
| Status | Use the value shown by your installation or issued for your app. |
| App ID | Use the value shown by your installation or issued for your app. |
| App Key | Use the value shown by your installation or issued for your app. |
| App Secret | Use the value shown by your installation or issued for your app. |
| Permissions | VALUABLE_ACCESS PHOTO_CONTENT GROUP_CONTENT LONG_ACCESS_TOKEN (source default; review necessity and actual granted access before requesting) |
| Callback URL | /integrations/ok/group |
Version: 1d0944d30f606782c9abf5b878224cdd3cd09b99
Open the source definitionAI, email, payments and storage
| Integration type | Setup and result to check |
|---|---|
| AI provider | Use the product’s actual provider/model/key settings. Check billing and allowance, then run one intended test generation. A saved API key is not proof the model is available. |
| Email / SMTP | Use the correct mail account/server settings, then send to a controlled test inbox using an authorized test action. Check delivery, not only queue creation. |
| Payments | Use the gateway’s supported test mode and test credentials first. Configure its exact webhook and verify checkout, provider confirmation, invoice/license state and retry behavior separately. |
| Storage | Use the configured disk/provider credentials and test upload, read and access restrictions with disposable files. |
| Custom domains | Follow the domain guide for DNS verification, routing and HTTPS. Domain verification is separate from OAuth app verification. |
Follow each product’s installation/admin guide for the actual settings location. These service accounts do not all require a social app-review submission.
Unofficial connections
Some StackPosts/MarkHub source versions include Instagram Unofficial or a WhatsApp Unofficial gateway. They are separate connection mechanisms. Do not describe them as provider-approved official API apps, and do not use an official OAuth review guide to claim approval for them. The reviewed Waziper Cloud edition uses Manual Cloud API.
These are fields and default paths found in the reviewed source version. An installed module or a source default does not prove platform approval. Copy the complete URL shown by your running installation; do not paste a path by itself into a developer console.
StackPosts — Instagram Unofficial / AppChannelInstagramUnofficial
| Setting label | Source information |
|---|---|
| Status | Use the value shown by your installation or issued for your app. |
Version: 1d0944d30f606782c9abf5b878224cdd3cd09b99
Open the source definitionMarkHub — WhatsApp Unofficial Gateway / WhatsAppUnofficialGateway
| Setting label | Source information |
|---|---|
| Status | Use the value shown by your installation or issued for your app. |
| Private Gateway URL | Use the value shown by your installation or issued for your app. |
| Shared secret | Use the value shown by your installation or issued for your app. |
| Signed callback URL | Use the value shown by your installation or issued for your app. |
Version: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88
Open the source definitionMarkHub — Instagram Unofficial / ChannelInstagramUnofficial
| Setting label | Source information |
|---|---|
| Status | Use the value shown by your installation or issued for your app. |
Version: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88
Open the source definitionCheck the installed version
Different products contain different modules and connection methods. If a provider is absent from the interface, confirm the installed edition and enabled modules with the administrator before attempting setup. No token, webhook or account was created or tested by this documentation update.