Issue Credential with Dock Certs API on Failed Task in Schema from Snowflake API

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

Trigger workflow on

Failed Task in Schema from the Snowflake 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 Snowflake 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 Failed Task in Schema trigger
1. Connect your Snowflake account
2. Configure timer
3. Select a Database
4. Select one or more Schema
5. Optional- Configure Task Name
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#

Failed Task in Schema on Snowflake

Description:Emit new events when a task fails in a database schema

Version:0.1.2

Key:snowflake-failed-task-in-schema

View on GitHub

Snowflake Overview#

Snowflake offers a cloud database and related tools to help developers create robust, secure, and scalable data warehouses. See Snowflake's Key Concepts & Architecture.

Getting Started

1. Create a user, role and warehouse in Snowflake

Snowflake recommends you create a new user, role, and warehouse when you integrate a third-party tool like Pipedream. This way, you can control permissions via the user / role, and separate Pipedream compute and costs with the warehouse. You can do this directly in the Snowflake UI.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

2. Enter those details in Pipedream

Visit https://pipedream.com/accounts. Click the button to Connect an App. Enter the required Snowflake account data.

You'll only need to connect your account once in Pipedream. You can connect this account to multiple workflows to run queries against Snowflake, insert data, and more.

3. Build your first workflow

Visit https://pipedream.com/new to build your first workflow. Pipedream workflows let you connect Snowflake with 1,000+ other apps. You can trigger workflows on Snowflake queries, sending results to Slack, Google Sheets, or any app that exposes an API. Or you can accept data from another app, transform it with Python, Node.js, Go or Bash code, and insert it into Snowflake.

Learn more at Pipedream University.

Trigger Code#

import common from "../common.mjs";

export default {
  ...common,
  props: {
    ...common.props,
    timer: {
      description: "Watch for failed tasks on this schedule",
      type: "$.interface.timer",
      default: {
        intervalSeconds: 15 * 60,
      },
    },
    database: {
      propDefinition: [
        common.props.snowflake,
        "database",
      ],
    },
    schemas: {
      propDefinition: [
        common.props.snowflake,
        "schema",
        (configuredProps) => ({
          database: configuredProps.database,
        }),
      ],
      type: "string[]",
    },
    taskName: {
      type: "string",
      label: "Task Name",
      description: "The name of the task to watch for failures. It allows you to use Regex to match multiple tasks.",
      optional: true,
    },
  },
  type: "source",
  key: "snowflake-failed-task-in-schema",
  // eslint-disable-next-line
  name: "Failed Task in Schema",
  description: "Emit new events when a task fails in a database schema",
  version: "0.1.2",
  async run() {
    await this.emitFailedTasks({
      database: this.database,
      schemas: this.schemas,
      taskName: this.taskName,
    });
  },
};

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
Snowflake	`snowflake`	`app`	This component uses the Snowflake app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`	Watch for failed tasks on this schedule
Database	`database`	`string`	Select a value from the drop down menu.
Schema	`schemas`	`string[]`	Select a value from the drop down menu.
Task Name	`taskName`	`string`	The name of the task to watch for failures. It allows you to use Regex to match multiple tasks.

Trigger Authentication#

Snowflake uses API keys for authentication. When you connect your Snowflake account, Pipedream securely stores the keys so you can easily authenticate to Snowflake APIs in both code and no-code steps.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

About Snowflake#

A data warehouse built for the cloud

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.