Issue Credential with Dock Certs API on New Message In Channels (Instant) from Slack API

Pipedream makes it easy to connect APIs for Dock Certs, Slack and 2,400+ other apps remarkably fast.

Trigger workflow on

New Message In Channels (Instant) from the Slack API

Next, do this

Issue Credential with the Dock Certs API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Slack trigger and Dock Certs action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Message In Channels (Instant) trigger
1. Connect your Slack account
2. Optional- Select one or more Channels
3. Configure slackApphook
4. Optional- Configure Resolve Names
5. Optional- Configure Ignore Bots
6. Optional- Configure Ignore replies in threads
Configure the Issue Credential action
1. Connect your Dock Certs account
2. Select a Issuer Profile
3. Optional- Configure Anchor
4. Optional- Configure Persist
5. Optional- Configure Password
6. Optional- Select a Template Design
7. Select a Type
8. Configure Credential Subject
9. Optional- Select a Registry
10. Optional- Configure Expiration Date
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Message In Channels (Instant) on Slack

Description:Emit new event when a new message is posted to one or more channels

Version:1.0.22

Key:slack-new-message-in-channels

View on GitHub

Slack Overview#

The Pipedream Slack app enables you to build event-driven workflows that interact with the Slack API. Once you authorize the Pipedream app's access to your workspace, you can use Pipedream workflows to perform common Slack actions or write your own code against the Slack API.

The Pipedream Slack app is not a typical app. You don't interact with it directly as a bot, and it doesn't add custom functionality to your workspace out of the box. It makes it easier to automate anything you'd typically use the Slack API for, using Pipedream workflows.

Automate posting updates to your team channels
Create a bot to answer common questions
Integrate with your existing tools and services
And much more!

Trigger Code#

import common from "../common/base.mjs";
import constants from "../common/constants.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  ...common,
  key: "slack-new-message-in-channels",
  name: "New Message In Channels (Instant)",
  version: "1.0.22",
  description: "Emit new event when a new message is posted to one or more channels",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    conversations: {
      propDefinition: [
        common.props.slack,
        "conversation",
      ],
      type: "string[]",
      label: "Channels",
      description: "Select one or more channels to monitor for new messages.",
      optional: true,
    },
    // eslint-disable-next-line pipedream/props-description,pipedream/props-label
    slackApphook: {
      type: "$.interface.apphook",
      appProp: "slack",
      async eventNames() {
        return this.conversations || [
          "message",
        ];
      },
    },
    resolveNames: {
      propDefinition: [
        common.props.slack,
        "resolveNames",
      ],
    },
    ignoreBot: {
      propDefinition: [
        common.props.slack,
        "ignoreBot",
      ],
    },
    ignoreThreads: {
      type: "boolean",
      label: "Ignore replies in threads",
      description: "Ignore replies to messages in threads",
      optional: true,
    },
  },
  methods: {
    ...common.methods,
    getSummary() {
      return "New message in channel";
    },
    async processEvent(event) {
      if (event.type !== "message") {
        console.log(`Ignoring event with unexpected type "${event.type}"`);
        return;
      }
      if (event.subtype && !constants.ALLOWED_MESSAGE_IN_CHANNEL_SUBTYPES.includes(event.subtype)) {
        // This source is designed to just emit an event for each new message received.
        // Due to inconsistencies with the shape of message_changed and message_deleted
        // events, we are ignoring them for now. If you want to handle these types of
        // events, feel free to change this code!!
        console.log("Ignoring message with subtype.");
        return;
      }
      if ((this.ignoreBot) && (event.subtype == "bot_message" || event.bot_id)) {
        return;
      }
      // There is no thread message type only the thread_ts field
      // indicates if the message is part of a thread in the event.
      if (this.ignoreThreads && event.thread_ts) {
        console.log("Ignoring reply in thread");
        return;
      }
      if (this.resolveNames) {
        if (event.user) {
          event.user_id = event.user;
          event.user = await this.getUserName(event.user);
        } else if (event.bot_id) {
          event.bot = await this.getBotName(event.bot_id);
        }
        event.channel_id = event.channel;
        event.channel = await this.getConversationName(event.channel);
        if (event.team) {
          event.team_id = event.team;
          event.team = await this.getTeamName(event.team);
        }
      }
      return event;
    },
  },
  sampleEmit,
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Slack	`slack`	`app`	This component uses the Slack app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`conversations`	`string[]`	Select a value from the drop down menu.
	`slackApphook`	`$.interface.apphook`
Resolve Names	`resolveNames`	`boolean`	Instead of returning `channel`, `team`, and `user` as IDs, return their human-readable names.
Ignore Bots	`ignoreBot`	`boolean`	Ignore messages from bots
Ignore replies in threads	`ignoreThreads`	`boolean`	Ignore replies to messages in threads

Trigger Authentication#

Slack uses OAuth authentication. When you connect your Slack account, Pipedream will open a popup window where you can sign into Slack and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Slack API.

Pipedream requests the following authorization scopes when you connect your account:

bookmarks:writecalls:readcalls:writechannels:historychannels:readchannels:writednd:readdnd:writeemoji:readfiles:readgroups:historygroups:readgroups:writeim:historyim:readim:writelinks:readlinks:writempim:historympim:readmpim:writepins:readpins:writereactions:readreactions:writereminders:readreminders:writeremote_files:readremote_files:sharestars:readstars:writeteam:readusergroups:readusergroups:writeusers:readusers:read.emailusers:writechat:write:botchat:write:usercommandsfiles:write:userusers.profile:writeusers.profile:readsearch:read

About Slack#

Slack is a channel-based messaging platform. With Slack, people can work together more effectively, connect all their software tools and services, and find the information they need to do their best work — all within a secure, enterprise-grade environment.

Action#

Issue Credential on Dock Certs

Description:Issue a new credential. [See the documentation](https://docs.api.dock.io/#credentials)

Version:0.0.1

Key:dock_certs-issue-credential

View on GitHub

Dock Certs Overview#

The Dock Certs API provides a means for issuing verifiable credentials and decentralized identities, which are essential for managing digital proofs of various qualifications, memberships, or certifications. Using Pipedream's integration capabilities, you can automate the process of creating, revoking, and verifying these credentials. With Pipedream's serverless architecture, you can set up triggers and actions that respond to events in real-time, orchestrate data flow between Dock Certs and other services, and manage credentials with minimal manual intervention.

Action Code#

import dockCerts from "../../dock_certs.app.mjs";
import { ConfigurationError } from "@pipedream/platform";

export default {
  key: "dock_certs-issue-credential",
  name: "Issue Credential",
  description: "Issue a new credential. [See the documentation](https://docs.api.dock.io/#credentials)",
  version: "0.0.1",
  type: "action",
  props: {
    dockCerts,
    issuerProfile: {
      propDefinition: [
        dockCerts,
        "profile",
      ],
    },
    anchor: {
      type: "boolean",
      label: "Anchor",
      description: "Whether to anchor the credential on the blockchain as soon as it is issued. Defaults to false.",
      default: false,
      optional: true,
    },
    persist: {
      type: "boolean",
      label: "Persist",
      description: "Whether to store an encrypted version of this credential with Dock Certs. Defaults to false, if true you must supply password.",
      default: false,
      optional: true,
    },
    password: {
      type: "string",
      label: "Password",
      description: "Password used to encrypt the credential if you choose to store it. The same password must be used to retrieve the credential contents. Dock does not store this password.",
      optional: true,
    },
    template: {
      propDefinition: [
        dockCerts,
        "templateDesign",
      ],
    },
    type: {
      propDefinition: [
        dockCerts,
        "credentialType",
      ],
    },
    subject: {
      type: "string",
      label: "Credential Subject",
      description: "A unique identifier of the recipient. Example: DID, Email Address, National ID Number, Employee ID, Student ID, etc.",
    },
    status: {
      propDefinition: [
        dockCerts,
        "registry",
      ],
      description: "Identifier of the credential's revocation registry",
      optional: true,
    },
    expirationDate: {
      type: "string",
      label: "Expiration Date",
      description: "The date and time in GMT that the credential expired is specified in RFC 3339 format. The default value of the expirationDate will be empty if the user does not provide it.",
      optional: true,
    },
  },
  async run({ $ }) {
    if (this.persist && !this.password) {
      throw new ConfigurationError("Password required if `persist` is `true`.");
    }

    const data = {
      anchor: this.anchor,
      persist: this.persist,
      password: this.password,
      template: this.template,
      credential: {
        type: [
          this.type,
        ],
        subject: {
          id: this.subject,
        },
        status: this.status,
        issuer: this.issuerProfile,
        expirationDate: this.expirationDate,
      },
    };

    const response = await this.dockCerts.issueCredential({
      data,
      $,
    });

    if (response) {
      $.export("$summary", `Successfully issued credential with ID ${response.id}.`);
    }

    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Dock Certs	`dockCerts`	`app`	This component uses the Dock Certs app.
Issuer Profile	`issuerProfile`	`string`	Select a value from the drop down menu.
Anchor	`anchor`	`boolean`	Whether to anchor the credential on the blockchain as soon as it is issued. Defaults to false.
Persist	`persist`	`boolean`	Whether to store an encrypted version of this credential with Dock Certs. Defaults to false, if true you must supply password.
Password	`password`	`string`	Password used to encrypt the credential if you choose to store it. The same password must be used to retrieve the credential contents. Dock does not store this password.
Template Design	`template`	`string`	Select a value from the drop down menu.
Type	`type`	`string`	Select a value from the drop down menu.
Credential Subject	`subject`	`string`	A unique identifier of the recipient. Example: DID, Email Address, National ID Number, Employee ID, Student ID, etc.
Registry	`status`	`string`	Select a value from the drop down menu.
Expiration Date	`expirationDate`	`string`	The date and time in GMT that the credential expired is specified in RFC 3339 format. The default value of the expirationDate will be empty if the user does not provide it.

Issue Credential with Dock Certs API on New Message In Channels (Instant) from Slack API

Pipedream makes it easy to connect APIs for Dock Certs, Slack and 2,400+ other apps remarkably fast.

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

1-24of2,400+apps by most popular

1
-
24
of
2,400+
apps by most popular