create_issue
Facts
Connectors.GitLab.functions.CreateIssue
GitLab
Input parameters
Required input parameters
confidential
boolean
RequiredSet the issue to be confidential and only be visible to team members with at least reporter access
gitlab_access_token
slack#/types/credential/oauth2
RequiredGitLab Access token. See the authentication section for details.
issue_type
string
RequiredIssue type
issue
incident
project_id
string
RequiredProject
title
string
RequiredTitle
Optional input parameters
description
string
OptionalDescription
milestone_id
string
OptionalMilestone
Output parameters
Required output parameters
confidential
boolean
RequiredConfidential
issue_iid
string
RequiredInternal issue ID
issue_reference
string
RequiredIssue reference
issue_type
string
RequiredIssue type
issue
incident
issue_url
string
RequiredIssue URL
title
string
RequiredTitle
Optional output parameters
description
string
OptionalDescription
milestone
string
OptionalThe Global ID of a milestone to assign the issue
Authentication
End-user authentication
User workflows that include a connector function relying on end-user authentication can only be started with a link trigger.
{
"github_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 the app.
Usage info
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:
import { Connectors } from "deno-slack-hub/mod.ts";
Finally, add the connector as a step in your workflow just like you would a Slack function.
SomeWorkflow.addStep(
Connectors.GitLab.functions.CreateIssue, {
//...
🧙🏼 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 X is referring to an unknown step output parameter Y
You can safely ignore this error; it will go away as soon as your workspace admin approves your request to use the connector.