Docs
Tutorials
Developer Program
Your apps

Update a feature flag's state

Connector functions are a new addition to Slack automations. We recommend understanding the systems and APIs you're integrating with before setup.

Facts

Update a feature flag's state

Schema: Connectors.Launchdarkly.functions.UpdateFeatureFlagState
Service: LaunchDarkly

Input parameters

Required parameters
launchdarkly_access_token
slack#/types/credential/oauth2
·Required
Determines whether this connector will use the credentials of the user starting the workflow or the credentials configured by an app collaborator. See the Authentication section on this page for details.

Example
{ credential_source: "END_USER" }
project_key
string
·Required
The key of the project in which the feature flag to update is located

Example
"project-key-123abc"
feature_flag_key
string
·Required
The key of the feature flag to update

Example
"feature-123abc"
environment_key
string
·Required
The environment associated with this feature flag

Example
"env123-123abc"
feature_flag_state
string
·Required
The state to update this feature flag to

Example
One of: "turnFlagOn", "turnFlagOff"
Optional parameters
comment
string
·Optional
Add comments

Output parameters

Required parameters
name
string
·Required
Feature flag name
description
string
·Required
Feature flag description
key
string
·Required
Feature flag key
environment_key
string
·Required
Environment key
comment
string
·Required
Comment
feature_flag_state
string
·Required
Feature flag state

Authentication

A connector's access token property specifies how the connector handles authentication.

End-user authentication

user Workflows that include a connector function relying on end-user authentication can can only be started with a link trigger.

launchdarkly_access_token: {
    credential_source: "END_USER"
}

End-user experience: User will be prompted to link their external account via OAuth when they first start the workflow that contains this connector.

Developer experience: Developer does not have to implement authentication in app.

Developer authentication 

launchdarkly_access_token: {
    credential_source: "DEVELOPER"
}

End-user experience: User can start a workflow containing the connector (they are not prompted to authenticate).

Developer experience: One of the app's collaborators configures external authentication via the CLI before sharing the app with users.

How to use

First, import Connectors from deno-slack-hub into your project's import_map.json file, like this:

{
  "imports": {
    "deno-slack-hub/": "https://deno.land/x/deno_slack_hub@2.2.0/",
    "deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.14.2/",
    "deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/",
  }
}

Next, import Connectors at the top of your workflow's definition file:

// my_workflow_file.ts
import { Connectors } from "deno-slack-hub/mod.ts";

Finally, add the connector as a step in your workflow just like you would a built-in Slack function.

SomeWorkflow.addStep(
  Connectors.Launchdarkly.functions.UpdateFeatureFlagState, {
  //...

🧙🏼 Your admin may need to approve the connector first. If your workspace has been configured to only allow admin-approved apps, the CLI will prompt you to send an admin approval request the first time you try to use a connector that hasn't been approved by an admin yet. While waiting for admin approval, the CLI may report an error like this:

Workflow function... is referring to an unknown step output parameter...

You can safely ignore this error; it will go away as soon as your workspace admin approves your request to use the connector.

Make your next big announcement beautiful.
Block Kit Builder will show you how to compose your JSON just so.