Configure Application Resources
Last updated
Last updated
Most of the resources and integrations used to configure your applications must be set up at the Console-level before they can be tied to an app. This is especially true for resources and integrations that require any sort of authentication: for security purposes, best practice dictates that things like API keys and account details be stored outside of the application.
Once a resource or integration is configured in the Console, it becomes available for configuration within an app. You can find the configuration interface in the Studio, under Settings. Some, but not all, of these resources can also be configured as part of the publication flow, although doing should only be done sparingly, as part of the confirmation process.
In this document, we'll walk through some common configuration fields, discuss when they might be used, and link to additional documentation that explains in more detail how to configure them.
Can be confirmed or re-configured during publication.
A Base Domain needs to be configured if any part of your application has a web component. It defines the domains of all links leading to any part of the application, including both Starting Links and Journey Links. For more on how how to configure a new Base Domain in the Console, see Custom Domains.
Can be confirmed or re-configured during publication.
A Voice Bot needs to be configured if your application sends or receives phone calls. Before configuring a Voice Bot at the application-level, a voice resource will need to be bought from Twilio and configured in the Console. For more on how this is done, see Connecting Twilio Numbers.
Can be confirmed or re-configured during publication.
A Chat Bot needs to be configured if your application sends or receives text messages. Before configuring a Chat Bot at the application-level, an SMS resource will need to be bought from Twilio and configured in the Console. For more on how this is done, see Connecting Twilio Numbers.
Cannot be confirmed or re-configured during publication.
An Email needs to be configured if your application sends outgoing emails at any point throughout the Journey. For more on how this is done, see Connecting Email Addresses
Cannot be confirmed or re-configured during publication.
Integrations need to be configured if you application connects to external data sources that require authentication.
There is a wide variety of external data sources that can integrate with your apps, and just a wide variety of ways to configure integrations in the Console. To get started, check out our First Party Integration Guides or Custom Integration Guides.
