slackapi / deno-slack-hub Goto Github PK

While integrating a JiraCloud connector into my Deno workflow, I'm missing how to pass custom field values to both create_issue and edit_issue connector functions.

If I use the same connector functions in a workflow builder, I can see an "additional inputs" section in the form.

Let me know if more detail is needed.

Hi,

I'm trying to use these connectors to quickly integrate a Slack app with some apis, however I'm getting the following error:

🚫 The provided manifest file does not validate against schema. Consult the additional errors field to locate specific issues (invalid_manifest)

Error Details:

1: Workflow function `knal_input_workflow` step `3` is referring to an unknown function `A04U5QUE5EX#/functions/get_random_gif` (undefined_wf_function_step)
Source: /workflows/knal_input_workflow/steps/3

I followed the setup steps in the README, is there another step I still need to do to import this function into my code as well?

Update: this only happens when I try to test the code locally using the cli slack run , if I deploy the app it works fine. So presumably I need to make this function known to my local environment somehow?

Hi there,

This is a question about the expected format for email_body in the above-mentioned connector.

I'm adding https://api.slack.com/reference/connectors/google.mail/send_email to a workflow on Slack's next-gen platform. The documentation shows email_body as a rich_text input.

The code sample below generates an email body that resembles a stringified JSON output:

sampleWorkflow
  .addStep(Connectors.GoogleMail.functions.SendEmail, {
    google_access_token: {
      credential_source: "END_USER",
    },
    recipients: ["[email protected]"],
    subject: "Hi there",
    email_body: "Test",
})

The generated email body from Gmail:

[{"text":{"text":"Test","type":"mrkdwn","verbatim":false},"type":"section","block_id":"oltZm"}]

Surprisingly, if I use the same connector function in Workflow Builder, the email_body comes from a rich text form field, the formatting works as expected.

Improve the test for the generation script

In the deno-slack-sdk we have added an integration test that validates the behavior of the generation script.

This is the test in question

It would be nice to add this capability here as well.

Source Deno version in GitHub Actions

Currently the GitHub Actions hard codes the deno-version value, Ideally we want the the deno-version value to be sourced dynamically from https://api.slack.com/slackcli/metadata.json 🔗

It is possible to set environment variable in a step this could be a potential solution to fetch, parse and set the deno-version

Context: #5 this comment