Hey there!
Is there an official way on how to smoothly onboard users to a Apps SDK app / plugin. Currently the process seems quite buggy and jumpy especially when the user does not have a ChatGPT Account yet. Furthermore if he has one, we would like to be able to provide them with a link to connect with the app including a CUSTOM prompt as soon as he clicks the use plugin button to have a seamless experience from a user’s perspective.
This is especially for ways where the app is not discovered through ChatGPT Plugin Directory itself but from external efforts.
At best would be a link to the Plugin Directory including a query param or anything to predefine the prompt that will be used when using the app via the button in the Plugin Directory.
Does this exist? Is this planned?
Hi welcome to the forum!
At the moment, there does not appear to be an official, documented onboarding flow that lets external sites open a specific Apps SDK app with a custom prompt prefilled or automatically submitted.
Parameters such as ?prompt= or ?q= are not documented as a supported integration mechanism for Custom GPT or app links, so relying on them would be fragile.
An official deep-link format for app discovery, account onboarding, app connection, and optional launch context would greatly improve the experience for users arriving from external websites.
Hi, Can’t you just give the user the URL to your plugin listing (https://chatgpt.com/plugins/<your_app_id> ) and then tell him to chat with @<your_app> on chatGPT
That works as a basic workaround for users who already have a ChatGPT account, but it doesn’t fully address the original use case.
It doesn’t improve the onboarding experience for users who don’t yet have a ChatGPT account, and there isn’t currently a supported way to pre-fill or automatically submit a custom prompt when launching an app. Users still need to complete account setup (if needed), connect the app, and start the conversation themselves.
An official deep-linking mechanism that could streamline discovery, account connection, and optional launch context would make external onboarding much smoother. We the users have shared similar feedback in the forum with the team, and it’s useful to hear additional developer interest in this workflow.