Anatomy of App Settings Module

The App Settings tab contains settings common to your app across all platforms. The settings are grouped under the following categories in the left menu.

CONNECTIVITY

Connection Settings: Contains your app’s database and backend connection settings.

  • DB connection string: A string containing the information required to connect to your app’s database. It typically includes the server address, database name, username, and password.
  • Backend URL: The URL used to access your app’s backend services.
Backend URL settings accept “IP” and “Port” information.
  • File Upload Path: Specifies the directory on the server where uploaded files will be stored. For example, a path such as /upload/user_documents/ can be specified for uploaded documents.
  • SAP Service Base URL: This is the base URL your application uses to connect to SAP services.

Data Source Configurations: Allows you to configure the connection settings for the data sources used by your application.

Rate Limiting: Allows you to limit the number of requests that can be made to your application within a specific time period.

STORAGE & SEARCH

Document Management: Contains the document management settings for your application.

Full-Text Search Engine: Contains the search engine settings used to enable full-text search in your application.

Bucket Upload: Ensures that files uploaded by the application are stored in the cloud.

  • Name: The name assigned to the bucket.
  • Type: The cloud provider to be used (AWS or Google).
  • Encryption Key: The key used to encrypt files.
  • Encryption IV: The initialization vector (IV) used during encryption.

Cache Settings: Improves the application’s data performance by enabling data caching and fast access.

  • Name: The name assigned to the cache configuration.
  • Type: The type of data provider to be used:
    • Redis: A memory-based system that provides fast data access and caching.
    • Mongo: A NoSQL, document-based database. It is flexible and scalable.
    • SQL: A relational database; it offers powerful querying and a table structure.
    • Memory: Stores data in temporary memory; data is deleted when the application is closed.
  • Connection Settings: The server and authentication credentials the cache will connect to.

Search Service: Used for data search and management operations in your applications.

  • Name: The name assigned to the created configuration.
  • Base URL: The base URL used to establish a connection with the search service. It enables the application to send search queries and receive results via the Search Service API.
  • Vector Database Service Port: The port number used by the vector-based database service. It is used to perform similarity-based searches (e.g., text-based searches) on large and complex datasets.
  • Python Service Port: The port number used by the Python service that facilitates communication between the Search Service and the vector database. It enables operations such as adding sources and performing searches.
  • Storage Path: Specifies the directory where the Search Service’s data, indexes, and results are stored.

IDENTITY & ACCESS

Authentication & Authorization: Includes authentication and authorization settings.

  • Password Policy: Allows you to specify the password length, complexity, and change frequency. Incorrect login attempts on this screen are displayed as warning notifications; this alerts the user without interrupting the workflow.
  • Google: Enables users to sign in to your app using their Google accounts.
  • Facebook: Enables users to sign in to your app using their Facebook accounts.
  • MSAL: Enables authentication using Microsoft accounts.
  • OTP: A one-time password used in two-factor authentication processes.
  • 2F Auth: When enabled, the authentication process becomes two-step. The first step is typically a password, while the second step is an OTP security code.
  • 2 Auth Duration: This is the validity period of the OTP or security code, which constitutes the second step in the two-factor authentication process.
  • Expire Old Sessions Upon New Login: This is a security feature that automatically terminates old sessions associated with an account when a user logs in with the same account.

Authentication Cookies: Contains the cookie settings used in the authentication process.

INTEGRATIONS

Mail: Provides services for sending, receiving, and managing email. By configuring different email providers, you can set up a secure and manageable email infrastructure in your application. Supported providers:

  • SMTP: Enables sending via the standard email protocol.
  • AWS (Amazon Web Services SES): Enables sending via AWS Simple Email Service.
  • Exchange Server: Provides sending, receiving, and management services via a Microsoft Exchange server.

AI: Contains settings for the services to be used for artificial intelligence functions in your application. OpenAI, Azure OpenAI, Gemini, and Serper Tool configurations are defined in this section.

Payment Method: Contains payment methods.

  • Stripe: An international payment platform you can use for online payment transactions.
  • Iyzico: A Turkey-based payment platform that makes it easy to manage online payments.
  • Param: Offers various payment methods for e-commerce sites, mobile apps, and other digital platforms.

WhatsApp Business: Contains WhatsApp Business API integration information. The WhatsApp Business API is a service that enables businesses to communicate more efficiently with their customers. You can access the necessary information via the Meta for Developers (Facebook for Developers) platform.

For WhatsApp Business account and app information:

  1. Create a WhatsApp Business account.
  2. Create an app via Meta for Developers.
  3. Open the WhatsApp Business setting in Config Manager and enter the following information using the Add New link:
    • Name: The descriptive name given to the configuration.
    • Account Id: The unique identifier for your WhatsApp Business account. It must be the same across all WhatsApp configurations.
    • App Id: The unique identifier of the app created via Meta for Developers; it is used to access the API.
    • App Secret: This is the secret key used to secure your app.
    • Access Token: This is the authentication token used to access the WhatsApp API. It can be obtained with or without an expiration date. If obtained with an expiration date, messages cannot be sent via the app created with Kuika once it expires.
    • Phone Number Id: This is the unique identifier of the phone number linked to your WhatsApp Business account.
    • Version Number: Specifies the version of the WhatsApp Business API being used. The default value is v21.0.

Sending messages and using templates:

  • A message template is created via the WhatsApp dashboard, and WhatsApp approval is obtained.
  • Template example:
    • Subject: Regarding the Status of Your Offer
    • Message: Congratulations! Your application has been approved. Please select one of the buttons below to indicate whether you accept or reject our offer.
    • Buttons: Accept, Reject
  • Approved templates are sent via the Send WhatsApp Business Message action on Kuika. For more information, please review our related content.

Template types: Parameters in WhatsApp message templates are selected when the template is created in Meta. These parameters are automatically imported into Kuika, where they can be configured to send messages.

  • Templates with buttons: Can only be used in steps with external assignments.
  • Templates without buttons: Can be used at any stage of the process.
Kuika currently supports only Quick Reply buttons. Other button types cannot be used.

Using Quick Reply:

  • Buttons used to advance the process must be of the Quick Reply (custom) type.
  • Each button must be paired with a mail interaction.

Invers CloudBoxx: Contains the necessary settings for the Invers CloudBoxx integration.

Google reCAPTCHA: Used to prevent activities such as spam and abuse.

  • Name: The name specified for the reCAPTCHA configuration.
  • Site Key: The public key that enables reCAPTCHA to work in your application.
  • Secret Key: The secret key used on the server side during reCAPTCHA verification processes.

MCP: Contains the settings for the MCP (Model Context Protocol) servers your application will use.

OPERATIONS

Swagger UI: Contains settings for the Swagger UI interface, where you can view and test your application’s APIs.

Elastic APM: Used to monitor the application’s runtime performance, transaction durations, and error and exception logs. With Elastic APM (Application Performance Monitoring) settings, operations within the application can be tracked on a per-service basis, performance bottlenecks can be analyzed, and monitoring can be segmented by environment (production, development, etc.). These settings become active when the application is set to Preview or Run, and by integrating with the Elastic APM Server, they enable the centralized collection of the application’s real-time performance data.

Notify Actions: Manages notifications and alerts in your application.

  • Name: The name assigned for the notification configuration.
  • Default Duration: Determines how long notifications will be displayed on the screen by default.
  • Success Duration: Specifies how long notifications displayed after successfully completed operations remain on the screen.
  • Info Duration: Specifies the duration of notifications displayed for informational purposes.
  • Warning Duration: Determines how long warning messages will be visible.
  • Error Duration: Specifies the duration for which error messages will be displayed.

Deeplink Setting: Contains the settings required to allow direct access (deep link) to a specific screen in your app.

Date & Time Formats: Determines the format in which date and time information is displayed in the app.

  • Date Format: Determines the date format. Example formats:
    • MM/DD/YYYY (07/09/2025)
    • DD-MM-YYYY (09-07-2025)
    • YYYY.MM.DD (2025.07.09)
  • Time Format: Allows you to choose whether the time is displayed in 24-hour or 12-hour (AM/PM) format. Example formats:
    • HH:MM (14:30)
    • HH:MM AM/PM (02:30 PM)