Create a task
| Schema: | Connectors.Wrike.functions.CreateATask |
|---|---|
| Service: | Wrike |
{ credential_source: "END_USER" }
A connector's access token property specifies how the connector handles authentication.
user Workflows that include a connector function relying on end-user authentication can can only be started with a link trigger.
wrike_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.
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.Wrike.functions.CreateATask, {
//...
🧙🏼 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.