> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/onboarding/integrated-onboarding/connect-button.md).
# Using Connect Button
The 360Dialog Connect Button simplifies **Integrated Onboarding (IO).** The button is customizable and, when clicked, triggers the Integrated Onboarding flow. It also simplifies handling the post-IO-flow redirect.
Partners using a different UI library or framework, or preferring their own implementation, can create their own Integrated Onboarding trigger and redirect the consumer by [following this guide.](/partner/onboarding/integrated-onboarding/using-custom-io.md)
## Requirements
* [x] Redirect URL must be set in the 360Dialog Hub. [See instructions here.](/partner/partner-api/overview.md#partner-hub-redirect-url)
* [x] Partner Hub webhook URL must be set. [See instructions here.](/partner/partner-api/overview.md#partner-hub-webhook)
### Direct-Paid Accounts
Clients of [Direct-Paid partner accounts](/partner/get-started/billing-models.md#direct-paid) will see a price detail and payment information page between the **Account Creation** and **Embedded Signup** steps.
The client needs to grant API key permission before the partner can generate an API key for them. Clients can give this permission during the Integrated Onboarding flow (pictured below), or in the 360Dialog Hub after onboarding.
API key permission request screen shown to clients of Direct-Paid partner accounts
## Implementation
{% stepper %}
{% step %}
### Use the connect button
There are two ways to use the 360Dialog Connect Button:
* This [**Demo App**](https://integrated-onboarding-demo.vercel.app/) can be used. Just fill in the partner ID and copy the button or link:
* Or include a script tag on your page:
```