Create Dashboard with Metabase API on Document Completed from Crove API

Pipedream makes it easy to connect APIs for Metabase, Crove and 2,900+ other apps remarkably fast.

Trigger workflow on

Document Completed from the Crove API

Next, do this

Create Dashboard with the Metabase 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 Crove trigger and Metabase action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Document Completed trigger
1. Connect your Crove account
2. Select a Template
Configure the Create Dashboard action
1. Connect your Metabase account
2. Configure Name
3. Optional- Configure Description
4. Optional- Select a Collection ID
5. Optional- Configure Collection Position
6. Optional- Configure Cache TTL
7. Optional- Configure Parameters
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#

Document Completed on Crove

Description:Triggers when a document is completed.

Version:1.0.2

Key:crove_app-document-completed

View on GitHub

Crove Overview#

The Crove API offers a suite of tools for automating document creation, customization, and management. Using Pipedream's integration capabilities, you can leverage Crove to generate tailored documents based on dynamic data inputs and trigger actions within other applications. Imagine auto-generating contracts when a deal is marked 'won' in a CRM, or creating personalized onboarding paperwork as soon as a new employee is added to your HR system. With Pipedream, you can connect Crove to a multitude of apps to streamline document workflows and enhance productivity.

Trigger Code#

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

export default {
  ...common,
  key: "crove_app-document-completed",
  name: "Document Completed",
  description: "Triggers when a document is completed.",
  version: "1.0.2",
  type: "source",
  methods: {
    ...common.methods,
    getEvents() {
      return [
        "document.completed",
      ];
    },
  },
};

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
Crove	`croveApp`	`app`	This component uses the Crove app.
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Template	`template_id`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

You can find your API key in the API Keys section of your Crove Workspace Settings.

About Crove#

Crove.app helps you to automate your repetitive business documents. With Crove you can create your repetitive business documents as intelligent templates that use variables and logical conditions.

Action#

Create Dashboard on Metabase

Description:Create a new Dashboard. [See the documentation](https://www.metabase.com/docs/latest/api#tag/apidashboard/post/api/dashboard/).

Version:0.0.3

Key:metabase-create-dashboard

View on GitHub

Metabase Overview#

The Metabase API opens a gateway to interact with Metabase programmatically, enabling you to automate reporting, dashboards, and data analysis operations. With Pipedream, you can harness this API to trigger workflows, manipulate data, and integrate with various other apps to create a seamless data ecosystem. Think of syncing Metabase insights with other tools, automating report generation, or reacting to events within your Metabase instance in real-time.

Action Code#

import app from "../../metabase.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "metabase-create-dashboard",
  name: "Create Dashboard",
  description: "Create a new Dashboard. [See the documentation](https://www.metabase.com/docs/latest/api#tag/apidashboard/post/api/dashboard/).",
  version: "0.0.3",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    app,
    name: {
      type: "string",
      label: "Name",
      description: "The name of the dashboard",
    },
    description: {
      type: "string",
      label: "Description",
      description: "Description of the dashboard",
      optional: true,
    },
    collectionId: {
      propDefinition: [
        app,
        "collectionId",
      ],
      optional: true,
    },
    collectionPosition: {
      type: "integer",
      label: "Collection Position",
      description: "Position within the collection (must be greater than zero)",
      min: 1,
      optional: true,
    },
    cacheTtl: {
      type: "integer",
      label: "Cache TTL",
      description: "Cache time-to-live in seconds (must be greater than zero)",
      min: 1,
      optional: true,
    },
    parameters: {
      type: "string[]",
      label: "Parameters",
      description: "Array of parameter definition objects.\n\n**Required properties:**\n- `id` (string) - Parameter identifier\n- `type` (string) - Parameter type (e.g., \"date/single\", \"text\", \"category\")\n\n**Optional properties:**\n- `name` (string) - Display name\n- `slug` (string) - URL-friendly identifier\n- `sectionId` (string) - Section grouping\n- `default` - Default value\n- `values_source_type` (enum) - \"static-list\", \"card\", or null\n- `values_source_config` (object) - Dynamic value configuration with `card_id`, `label_field`, `value_field`, `values`\n- `temporal_units` (array) - Time-based parameter units\n\n**Example:** `{\"id\": \"date_param\", \"type\": \"date/single\", \"name\": \"Date Filter\", \"slug\": \"date_filter\", \"default\": \"2024-01-01\"}`",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      app,
      name,
      description,
      collectionId,
      collectionPosition,
      cacheTtl,
      parameters,
    } = this;

    const response = await app.createDashboard({
      $,
      data: {
        name,
        description,
        collection_id: collectionId,
        collection_position: collectionPosition,
        cache_ttl: cacheTtl,
        parameters: utils.parseArray(parameters),
      },
    });

    $.export("$summary", `Successfully created dashboard 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
Metabase	`app`	`app`	This component uses the Metabase app.
Name	`name`	`string`	The name of the dashboard
Description	`description`	`string`	Description of the dashboard
Collection ID	`collectionId`	`string`	Select a value from the drop down menu.
Collection Position	`collectionPosition`	`integer`	Position within the collection (must be greater than zero)
Cache TTL	`cacheTtl`	`integer`	Cache time-to-live in seconds (must be greater than zero)
Parameters	`parameters`	`string[]`	Array of parameter definition objects. Required properties: `id` (string) - Parameter identifier `type` (string) - Parameter type (e.g., "date/single", "text", "category") Optional properties: `name` (string) - Display name `slug` (string) - URL-friendly identifier `sectionId` (string) - Section grouping `default` - Default value `values_source_type` (enum) - "static-list", "card", or null `values_source_config` (object) - Dynamic value configuration with `card_id`, `label_field`, `value_field`, `values` `temporal_units` (array) - Time-based parameter units Example: `{"id": "date_param", "type": "date/single", "name": "Date Filter", "slug": "date_filter", "default": "2024-01-01"}`