Check for existence of key with Data Stores API on New Zapier Step Triggered (Instant) from Typebot API

Pipedream makes it easy to connect APIs for Data Stores, Typebot and 2,200+ other apps remarkably fast.

Trigger workflow on

New Zapier Step Triggered (Instant) from the Typebot API

Next, do this

Check for existence of key with the Data Stores 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 Typebot trigger and Data Stores action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Zapier Step Triggered (Instant) trigger
1. Connect your Typebot account
2. Select a Workspace ID
3. Select a Typebot ID
4. Select a Block ID
Configure the Check for existence of key action
1. Connect your Data Stores account
2. Configure Data Store
3. Select a Key
4. Optional- Select a Create a new record if the key is not found?
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 Zapier Step Triggered (Instant) on Typebot

Description:Emit new event when a zapier step is triggered. [See the docs](https://docs.typebot.io/api/subscribe-to-webhook-block)

Version:0.0.1

Key:typebot-zapier-step-triggered

View on GitHub

Typebot Overview#

Typebot is a conversational form builder that allows you to create interactive and engaging forms for data collection. With Typebot API on Pipedream, you can automate the processing of form submissions, synchronize data with other services, and trigger customized workflows. Utilize the data gathered from Typebot in real-time, enrich it with other services, and streamline processes like lead generation, surveys, and feedback collection.

Trigger Code#

import app from "../../typebot.app.mjs";

export default {
  key: "typebot-zapier-step-triggered",
  name: "New Zapier Step Triggered (Instant)",
  description: "Emit new event when a zapier step is triggered. [See the docs](https://docs.typebot.io/api/subscribe-to-webhook-block)",
  type: "source",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    app,
    db: "$.service.db",
    http: "$.interface.http",
    workspaceId: {
      propDefinition: [
        app,
        "workspaceId",
      ],
    },
    typebotId: {
      propDefinition: [
        app,
        "typebotId",
        ({ workspaceId }) => ({
          workspaceId,
        }),
      ],
    },
    blockId: {
      propDefinition: [
        app,
        "blockId",
        ({ typebotId }) => ({
          typebotId,
        }),
      ],
    },
  },
  hooks: {
    async activate() {
      const {
        typebotId,
        blockId,
        http: { endpoint: url },
      } = this;
      await this.app.subscribeToWebhookBlock({
        typebotId,
        blockId,
        data: {
          url,
        },
      });
    },
    async deactivate() {
      const {
        typebotId,
        blockId,
      } = this;
      await this.app.unsubscribeFromWebhookBlock({
        typebotId,
        blockId,
      });
    },
  },
  methods: {
    generateMetadata(resource) {
      const ts = Date.parse(resource.submittedAt);
      return {
        id: ts,
        ts,
        summary: `New Step Submitted at ${resource.submittedAt}`,
      };
    },
  },
  async run({ body }) {
    const meta = this.generateMetadata(body);
    this.$emit(body, meta);
  },
};

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
Typebot	`app`	`app`	This component uses the Typebot app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
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.
Workspace ID	`workspaceId`	`string`	Select a value from the drop down menu.
Typebot ID	`typebotId`	`string`	Select a value from the drop down menu.
Block ID	`blockId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

To retrieve your API token,

Navigate to your Typebot account and sign in
Go to “Settings & Members” > “My account” > “API tokens”

About Typebot#

Typebot gives you powerful blocks to create unique chat experiences. Embed them anywhere on your web/mobile apps and start collecting results like magic.

Action#

Check for existence of key on Data Stores

Description:Check if a key exists in your [Pipedream Data Store](https://pipedream.com/data-stores/) or create one if it doesn't exist.

Version:0.1.2

Key:data_stores-has-key-or-create

View on GitHub

Data Stores Overview#

Data Stores are a key-value store that allow you to persist state and share data across workflows. You can perform CRUD operations, enabling dynamic data management within your serverless architecture. Use it to save results from API calls, user inputs, or interim data; then read, update, or enrich this data in subsequent steps or workflows. Data Stores simplify stateful logic and cross-workflow communication, making them ideal for tracking process statuses, aggregating metrics, or serving as a simple configuration store.

Action Code#

import app from "../../data_stores.app.mjs";

export default {
  key: "data_stores-has-key-or-create",
  name: "Check for existence of key",
  description: "Check if a key exists in your [Pipedream Data Store](https://pipedream.com/data-stores/) or create one if it doesn't exist.",
  version: "0.1.2",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
    key: {
      propDefinition: [
        app,
        "key",
        ({ dataStore }) => ({
          dataStore,
        }),
      ],
      description: "Enter the key you'd like to check.",
    },
    addRecordIfNotFound: {
      propDefinition: [
        app,
        "addRecordIfNotFound",
      ],
    },
  },
  async additionalProps() {
    const props = {};
    if (this.app.shouldAddRecord(this.addRecordIfNotFound)) {
      props.value = app.propDefinitions.value;
    }
    return props;
  },
  async run({ $ }) {
    if (await this.dataStore.has(this.key)) {
      $.export("$summary", `Key \`${this.key}\` exists.`);

      return {
        existingKeyFound: true,
        newKeyCreated: false,
      };
    }

    if (!this.app.shouldAddRecord(this.addRecordIfNotFound)) {
      $.export("$summary", `Key \`${this.key}\` does not exist.`);

      return {
        existingKeyFound: false,
        newKeyCreated: false,
      };
    }

    const parsedValue = this.app.parseValue(this.value);
    await this.dataStore.set(this.key, parsedValue);
    $.export("$summary", `Key \`${this.key}\` was not found. Successfully added a new record.`);

    return {
      existingKeyFound: false,
      newKeyCreated: true,
      value: parsedValue,
    };
  },
};

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
Data Stores	`app`	`app`	This component uses the Data Stores app.
Data Store	`dataStore`	`data_store`	Select an existing Data Store or create a new one.
Key	`key`	`string`	Select a value from the drop down menu.
Create a new record if the key is not found?	`addRecordIfNotFound`	`string`	Select a value from the drop down menu:`YesNo`