Tasks

Manage Configs

Manages organization configuration and reads user preferences. Authentication is forwarded automatically from the running action.

This task manages organization configurations such as credentials and notification settings, and reads user preferences. Core forwards the action's authentication and org context to Manage automatically.

# Usage Scenarios

This task is used to automate setup and configuration of various organization settings in Stubber. It supports creating, reading, updating, and deleting configurations for different resources.
Examples include:

• Creating a new webchat profile
• Updating an existing webchat profile
• Reading user preferences inside a stub action

# Supported Manage Config Types

The following configuration types are currently supported:

• Notifications
  • Webchat profiles (/notifications/webchat/profiles)
• User preferences (read only)
  • Profile including preferences (/rolodex/profile)
  • Flowpilot settings (/rolodex/profile/flowpilot-settings)

# Read user preferences

Use operation: "read" with one of the supported Rolodex targets:

Name the task get_user_preferences. In a later task, read the preferences using:

        ~~stubpost.tasks.get_user_preferences.payload.profile.user_preferences

      

For /rolodex/profile/flowpilot-settings, the result is instead in stubpost.tasks.get_user_preferences.payload.flowpilot_settings.

No token or credential needs to be configured on the task. The action's authentication determines whose preferences are returned; lookup by another user identifier is not supported. Only read is allowed for these exact Rolodex targets. Other Rolodex paths or operations return rolodex_only_allows_reading_user_preferences.

See User Preferences for the full task example, result, and execution identity details. These targets require the Core user-preferences task update in the stub's environment.

# Basic usage

# Parameters

# target_path

string

The path to the resource being managed. This specifies the type and location of the configuration. For UUID-specific operations, you can either include the UUID in the path or provide it as a parameter.

Examples:

• /notifications/webchat/profiles - for general profile operations
• /notifications/webchat/profiles/{{profile_uuid}} - for specific profile operations

# operation

string

The operation to perform on the configuration. Available operations:

• create - Create a new configuration
• read - Read an existing configuration
• update - Update an existing configuration
• delete - Delete an existing configuration

# params

object

Resource specific parameters to the operation being performed. For read, update, and delete operations, this typically includes the UUID of the resource. For create and update operations, this includes the configuration data.

# Examples

Create a webchat profile

Update a webchat profile

Read a webchat profile (using params)

Read a webchat profile (using target_path)