Analyze Text with Tisane Labs API on Changes to Specific Files from Google Drive API

Pipedream makes it easy to connect APIs for Tisane Labs, Google Drive and 2,200+ other apps remarkably fast.

Trigger workflow on

Changes to Specific Files from the Google Drive API

Next, do this

Analyze Text with the Tisane Labs 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 Google Drive trigger and Tisane Labs action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Changes to Specific Files trigger
1. Connect your Google Drive account
2. Optional- Configure Drive
3. Configure Push notification renewal schedule
4. Select one or more Files
5. Configure intervalAlert
6. Optional- Configure Minimum Interval Per File
7. Select one or more Types of updates
Configure the Analyze Text action
1. Connect your Tisane Labs account
2. Select a Language
3. Configure Content
4. Optional- Select a Format
5. Optional- Configure Disable Spellcheck
6. Optional- Configure Lowercase Spellcheck Only
7. Optional- Configure Minimum Generic Frequency
8. Optional- Configure Subscope
9. Optional- Configure Abuse
10. Optional- Configure Sentiment
11. Optional- Configure Document Sentiment
12. Optional- Configure Entities
13. Optional- Configure Topics
14. Optional- Configure Words
15. Optional- Configure Fetch Definitions
16. Optional- Configure Parse
17. Optional- Configure Deterministic
18. Optional- Configure Snippets
19. Optional- Configure Explain
20. Optional- Select a Feature Standard
21. Optional- Select a Topic Standard
22. Optional- Select a Sentiment Analysis Type
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#

Changes to Specific Files on Google Drive

Description:Watches for changes to specific files, emitting an event when a change is made to one of those files. To watch for changes to [shared drive](https://support.google.com/a/users/answer/9310351) files, use the **Changes to Specific Files (Shared Drive)** source instead.

Version:0.2.3

Key:google_drive-changes-to-specific-files

View on GitHub

Google Drive Overview#

The Google Drive API on Pipedream allows you to automate various file management tasks, such as creating, reading, updating, and deleting files within your Google Drive. You can also share files, manage permissions, and monitor changes to files and folders. This opens up possibilities for creating workflows that seamlessly integrate with other apps and services, streamlining document handling, backup processes, and collaborative workflows.

Trigger Code#

import cronParser from "cron-parser";
import sampleEmit from "./test-event.mjs";
import includes from "lodash/includes.js";
import { v4 as uuid } from "uuid";
import { MY_DRIVE_VALUE } from "../../common/constants.mjs";
import changesToSpecificFiles from "../changes-to-specific-files-shared-drive/changes-to-specific-files-shared-drive.mjs";

/**
 * This source uses the Google Drive API's
 * {@link https://developers.google.com/drive/api/v3/reference/files/watch files: watch}
 * endpoint to subscribe to changes to specific files in the user's drive.
 */
export default {
  ...changesToSpecificFiles,
  key: "google_drive-changes-to-specific-files",
  name: "Changes to Specific Files",
  description: "Watches for changes to specific files, emitting an event when a change is made to one of those files. To watch for changes to [shared drive](https://support.google.com/a/users/answer/9310351) files, use the **Changes to Specific Files (Shared Drive)** source instead.",
  version: "0.2.3",
  type: "source",
  // Dedupe events based on the "x-goog-message-number" header for the target channel:
  // https://developers.google.com/drive/api/v3/push#making-watch-requests
  dedupe: "unique",
  props: {
    ...changesToSpecificFiles.props,
    drive: {
      type: "string",
      label: "Drive",
      description: "Defaults to `My Drive`. To use a [Shared Drive](https://support.google.com/a/users/answer/9310351), use the **Changes to Specific Files (Shared Drive)** source instead.",
      optional: true,
      default: MY_DRIVE_VALUE,
    },
    updateTypes: {
      propDefinition: [
        changesToSpecificFiles.props.googleDrive,
        "updateTypes",
      ],
    },
  },
  hooks: {
    ...changesToSpecificFiles.hooks,
    async activate() {
      // Called when a component is created or updated. Handles all the logic
      // for starting and stopping watch notifications tied to the desired
      // files.

      // You can pass the same channel ID in watch requests for multiple files, so
      // our channel ID is fixed for this component to simplify the state we have to
      // keep track of.
      const channelID = uuid();

      // Subscriptions are keyed on Google's resourceID, "an opaque value that
      // identifies the watched resource". This value is included in request
      // headers, allowing us to look up the watched resource.
      let subscriptions = this._getSubscriptions() || {};

      const files = this.files;
      for (const fileID of files) {
        const {
          expiration,
          resourceId,
        } = await this.googleDrive.activateFileHook(
          channelID,
          this.http.endpoint,
          fileID,
        );
        // The fileID must be kept with the subscription metadata so we can
        // renew the watch request for this specific file when it expires.
        subscriptions[resourceId] = {
          expiration,
          fileID,
        };
      }

      // Save metadata on the subscription so we can stop / renew later
      this._setSubscriptions(subscriptions);
      this._setChannelID(channelID);
    },
    async deactivate() {
      const channelID = this._getChannelID();
      if (!channelID) {
        console.log(
          "Channel not found, cannot stop notifications for non-existent channel",
        );
        return;
      }

      const subscriptions = this._getSubscriptions() || {};
      for (const resourceId of Object.keys(subscriptions)) {
        await this.googleDrive.stopNotifications(channelID, resourceId);
      }

      // Reset DB state
      this._setSubscriptions({});
      this._setChannelID(null);
    },
  },
  methods: {
    ...changesToSpecificFiles.methods,
    _getSubscriptions() {
      return this.db.get("subscriptions") || {};
    },
    _setSubscriptions(subscriptions) {
      this.db.set("subscriptions", subscriptions);
    },
    _getNextTimerEventTimestamp(event) {
      if (event.cron) {
        return cronParser
          .parseExpression(event.cron)
          .next()
          .getTime();
      }
      if (event.interval_seconds) {
        return Date.now() + event.interval_seconds * 1000;
      }
    },
    async renewFileSubscriptions(event) {
      const subscriptions = this._getSubscriptions() || {};
      const channelID = this._getChannelID();
      const newChannelID = uuid();

      const nextRunTimestamp = this._getNextTimerEventTimestamp(event);

      for (const [
        currentResourceId,
        metadata,
      ] of Object.entries(subscriptions)) {
        const { fileID } = metadata;

        const subscription = {
          ...metadata,
          resourceId: currentResourceId,
        };
        const {
          expiration,
          resourceId,
        } = await this.googleDrive.renewFileSubscription(
          subscription,
          this.http.endpoint,
          channelID,
          newChannelID,
          fileID,
          nextRunTimestamp,
        );
        subscriptions[resourceId] = {
          expiration,
          fileID,
        };
      }
      this._setSubscriptions(subscriptions);
      this._setChannelID(newChannelID);
    },
  },
  async run(event) {
    // This function is polymorphic: it can be triggered as a cron job, to make sure we renew
    // watch requests for specific files, or via HTTP request (the change payloads from Google)

    // Component was invoked by timer
    if (event.timestamp) {
      return this.renewFileSubscriptions(event);
    }

    const channelID = this._getChannelID();
    let subscriptions = this._getSubscriptions() || {};

    const { headers } = event;

    if (
      !headers["x-goog-resource-state"] ||
      !headers["x-goog-resource-id"] ||
      !headers["x-goog-resource-uri"] ||
      !headers["x-goog-message-number"]
    ) {
      console.log("Request missing necessary headers: ", headers);
      return;
    }

    const incomingChannelID = headers["x-goog-channel-id"];
    if (incomingChannelID !== channelID) {
      console.log(
        `Channel ID of ${incomingChannelID} not equal to deployed component channel of ${channelID}`,
      );
      return;
    }

    if (subscriptions[headers["x-goog-resource-id"]] === undefined) {
      console.log(
        `Resource ID of ${headers["x-goog-resource-id"]} not currently being tracked. Exiting`,
      );
      return;
    }

    if (!includes(this.updateTypes, headers["x-goog-resource-state"])) {
      console.log(
        `Update type ${headers["x-goog-resource-state"]} not in list of updates to watch: `,
        this.updateTypes,
      );
      return;
    }

    // We observed false positives where a single change to a document would trigger two changes:
    // one to "properties" and another to "content,properties". But changes to properties
    // alone are legitimate, most users just won't want this source to emit in those cases.
    // If x-goog-changed is _only_ set to "properties", only move on if the user set the prop
    if (
      !this.watchForPropertiesChanges &&
      headers["x-goog-changed"] === "properties"
    ) {
      console.log(
        "Change to properties only, which this component is set to ignore. Exiting",
      );
      return;
    }

    const file = await this.googleDrive.getFileMetadata(
      headers["x-goog-resource-uri"],
    );

    if (!file || !Object.keys(file).length) {
      console.log("No file metadata returned, nothing to emit");
      return;
    }

    const [
      checkedFile,
    ] = this.checkMinimumInterval([
      file,
    ]);
    if (checkedFile) {
      this.processChange(file, headers);
    }
  },
  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
Google Drive	`googleDrive`	`app`	This component uses the Google Drive 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.
Drive	`drive`	`string`	Defaults to `My Drive`. To use a Shared Drive, use the Changes to Specific Files (Shared Drive) source instead.
Push notification renewal schedule	`timer`	`$.interface.timer`	The Google Drive API requires occasional renewal of push notification subscriptions. This runs in the background, so you should not need to modify this schedule.
Files	`files`	`string[]`	Select a value from the drop down menu.
Minimum Interval Per File	`perFileInterval`	`integer`	How many minutes to wait until the same file can emit another event. If set to `0`, this interval is disabled and all events will be emitted.
Types of updates	`updateTypes`	`string[]`	Select a value from the drop down menu:`{ "label": "'sync' - A channel was successfully created. You can expect to start receiving notifications for it.", "value": "sync" }{ "label": "'add' - A resource was created or shared.", "value": "add" }{ "label": "'remove' - An existing resource was deleted or unshared.", "value": "remove" }{ "label": "'update' - One or more properties (metadata) of a resource have been updated.", "value": "update" }{ "label": "'trash' - A resource has been moved to the trash.", "value": "trash" }{ "label": "'untrash' - A resource has been removed from the trash.", "value": "untrash" }{ "label": "'change' - One or more changelog items have been added.", "value": "change" }`

Trigger Authentication#

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

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

https://www.googleapis.com/auth/drive

About Google Drive#

Google Drive is a file storage and synchronization service which allows you to create and share your work online, and access your documents from anywhere.

Action#

Analyze Text on Tisane Labs

Description:Analyze text for language, entities, sentiment, and other insights. [See the documentation](https://docs.tisane.ai/#561264c5-6dbe-4bde-aba3-7defe837989f)

Version:0.0.1

Key:tisane_labs-analyze-text

View on GitHub

Tisane Labs Overview#

The Tisane Labs API offers advanced text analysis capabilities, focusing on abusive content detection and linguistic insights. With it, you can automate content moderation, extract entities, detect the sentiment, and identify the language of the text. In Pipedream, Tisane Labs API can be integrated into workflows to process text from various sources such as user comments, support tickets, or social media posts. By leveraging Pipedream's serverless platform, you can create real-time, event-driven applications that respond to text analyses, connect with other services, and perform actions based on the insights gained from the Tisane Labs API.

Action Code#

import tisaneLabs from "../../tisane_labs.app.mjs";

export default {
  key: "tisane_labs-analyze-text",
  name: "Analyze Text",
  description: "Analyze text for language, entities, sentiment, and other insights. [See the documentation](https://docs.tisane.ai/#561264c5-6dbe-4bde-aba3-7defe837989f)",
  version: "0.0.1",
  type: "action",
  props: {
    tisaneLabs,
    language: {
      propDefinition: [
        tisaneLabs,
        "language",
      ],
    },
    content: {
      type: "string",
      label: "Content",
      description: "The content to analyze",
    },
    format: {
      propDefinition: [
        tisaneLabs,
        "format",
      ],
    },
    disableSpellcheck: {
      type: "boolean",
      label: "Disable Spellcheck",
      description: "Determines whether the automatic spellchecking is to be disabled. Default: `false`",
      default: false,
      optional: true,
    },
    lowercaseSpellcheckOnly: {
      type: "boolean",
      label: "Lowercase Spellcheck Only",
      description: "Determines whether the automatic spellchecking is only to be applied to words in lowercase. Default: `false`",
      default: false,
      optional: true,
    },
    minGenericFrequency: {
      type: "integer",
      label: "Minimum Generic Frequency",
      description: "Allows excluding more esoteric terms; The valid values are 0 thru 10.",
      min: 0,
      max: 10,
      optional: true,
    },
    subscope: {
      type: "boolean",
      label: "Subscope",
      description: "Enables sub-scope parsing, for scenarios like hashtag, URL parsing, and obfuscated content (e.g. ihateyou). Default: `false`",
      default: false,
      optional: true,
    },
    abuse: {
      type: "boolean",
      label: "Abuse",
      description: "Output instances of abusive conten. Default: `true`",
      default: true,
      optional: true,
    },
    sentiment: {
      type: "boolean",
      label: "Sentiment",
      description: "Output sentiment-bearing snippets. Default: `true`",
      default: true,
      optional: true,
    },
    documentSentiment: {
      type: "boolean",
      label: "Document Sentiment",
      description: "output document-level sentiment. Default: `false`",
      default: false,
      optional: true,
    },
    entities: {
      type: "boolean",
      label: "Entities",
      description: "Output entities. Default: `true`",
      default: true,
      optional: true,
    },
    topics: {
      type: "boolean",
      label: "Topics",
      description: "Output topics. Default: `true`",
      default: true,
      optional: true,
    },
    words: {
      type: "boolean",
      label: "Words",
      description: "Output the lexical chunks / words for every sentence. Default: `false`",
      default: false,
      optional: true,
    },
    fetchDefinitions: {
      type: "boolean",
      label: "Fetch Definitions",
      description: "Include definitions of the words in the output. Only relevant when the `words` setting is `true`. Default: `false",
      default: false,
      optional: true,
    },
    parses: {
      type: "boolean",
      label: "Parse",
      description: "Output parse forests of phrases",
      optional: true,
    },
    deterministic: {
      type: "boolean",
      label: "Deterministic",
      description: "Whether the n-best senses and n-best parses are to be output in addition to the detected sense. If `true`, only the detected sense will be output. Default: `true`",
      default: true,
      optional: true,
    },
    snippets: {
      type: "boolean",
      label: "Snippets",
      description: "Include the text snippets in the abuse, sentiment, and entities sections. Default: `false`",
      default: false,
      optional: true,
    },
    explain: {
      type: "boolean",
      label: "Explain",
      description: "If `true`, a reasoning for the abuse and sentiment snippets is provided when possible",
      optional: true,
    },
    featureStandard: {
      propDefinition: [
        tisaneLabs,
        "featureStandard",
      ],
    },
    topicStandard: {
      propDefinition: [
        tisaneLabs,
        "topicStandard",
      ],
    },
    sentimentAnalysisType: {
      propDefinition: [
        tisaneLabs,
        "sentimentAnalysisType",
      ],
    },
  },
  async run({ $ }) {
    const response = await this.tisaneLabs.analyzeText({
      data: {
        language: this.language,
        content: this.content,
        settings: {
          format: this.format,
          disable_spellcheck: this.disableSpellcheck,
          lowercase_spellcheck_only: this.lowercaseSpellcheckOnly,
          min_generic_frequency: this.minGenericFrequency,
          subscope: this.subscope,
          abusse: this.abuse,
          sentiment: this.sentiment,
          document_sentiment: this.documentSentiment,
          entities: this.entities,
          topics: this.topics,
          words: this.words,
          fetch_definitions: this.fetchDefinitions,
          parses: this.parses,
          deterministic: this.deterministic,
          snippets: this.snippets,
          explain: this.explain,
          feature_standard: this.featureStandard,
          topic_standard: this.topicStandard,
          sentiment_analysis_type: this.sentimentAnalysisType,
        },
      },
      $,
    });

    if (response) {
      $.export("$summary", "Successfully analyzed text.");
    }

    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
Tisane Labs	`tisaneLabs`	`app`	This component uses the Tisane Labs app.
Language	`language`	`string`	Select a value from the drop down menu.
Content	`content`	`string`	The content to analyze
Format	`format`	`string`	Select a value from the drop down menu:`{ "label": "Review", "value": "review" }{ "label": "Dialog", "value": "dialog" }{ "label": "Shortpost", "value": "shortpost" }{ "label": "Longform", "value": "longform" }{ "label": "Proofread", "value": "proofread" }{ "label": "Alias", "value": "alias" }{ "label": "Search", "value": "search" }`
Disable Spellcheck	`disableSpellcheck`	`boolean`	Determines whether the automatic spellchecking is to be disabled. Default: `false`
Lowercase Spellcheck Only	`lowercaseSpellcheckOnly`	`boolean`	Determines whether the automatic spellchecking is only to be applied to words in lowercase. Default: `false`
Minimum Generic Frequency	`minGenericFrequency`	`integer`	Allows excluding more esoteric terms; The valid values are 0 thru 10.
Subscope	`subscope`	`boolean`	Enables sub-scope parsing, for scenarios like hashtag, URL parsing, and obfuscated content (e.g. ihateyou). Default: `false`
Abuse	`abuse`	`boolean`	Output instances of abusive conten. Default: `true`
Sentiment	`sentiment`	`boolean`	Output sentiment-bearing snippets. Default: `true`
Document Sentiment	`documentSentiment`	`boolean`	output document-level sentiment. Default: `false`
Entities	`entities`	`boolean`	Output entities. Default: `true`
Topics	`topics`	`boolean`	Output topics. Default: `true`
Words	`words`	`boolean`	Output the lexical chunks / words for every sentence. Default: `false`
Fetch Definitions	`fetchDefinitions`	`boolean`	Include definitions of the words in the output. Only relevant when the `words` setting is `true`. Default: `false
Parse	`parses`	`boolean`	Output parse forests of phrases
Deterministic	`deterministic`	`boolean`	Whether the n-best senses and n-best parses are to be output in addition to the detected sense. If `true`, only the detected sense will be output. Default: `true`
Snippets	`snippets`	`boolean`	Include the text snippets in the abuse, sentiment, and entities sections. Default: `false`
Explain	`explain`	`boolean`	If `true`, a reasoning for the abuse and sentiment snippets is provided when possible
Feature Standard	`featureStandard`	`string`	Select a value from the drop down menu:`{ "label": "Universal Dependencies tags", "value": "ud" }{ "label": "Penn treebank tags", "value": "penn" }{ "label": "Tisane native feature codes", "value": "native" }{ "label": "Tisane native feature descriptions", "value": "description" }`
Topic Standard	`topicStandard`	`string`	Select a value from the drop down menu:`{ "label": "IPTC topic taxonomy code", "value": "iptc_code" }{ "label": "IPTC topic taxonomy description", "value": "iptc_description" }{ "label": "IAB topic taxonomy code", "value": "iab_code" }{ "label": "IAB topic taxonomy description", "value": "iab_description" }{ "label": "Tisane domain description, coming from the family description", "value": "native" }`
Sentiment Analysis Type	`sentimentAnalysisType`	`string`	Select a value from the drop down menu:`{ "label": "Products and Services", "value": "products_and_services" }{ "label": "Entity", "value": "entity" }{ "label": "Creative Content Review", "value": "creative_content_review" }{ "label": "Political Essay", "value": "political_essay" }`

Action Authentication#

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

About Tisane Labs#

Home of cutting edge, explainable AI software that turns unstructured content into meaningful insights.

More Ways to Connect Tisane Labs + Google Drive#

Other Popular Integrations#

Detect Language with Tisane Labs API on Changes to Specific Files from Google Drive API

Google Drive + Tisane Labs

Analyze Text with Tisane Labs API on Changes to Specific Files from Google Drive API

Pipedream makes it easy to connect APIs for Tisane Labs, Google Drive and 2,200+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,200+apps by most popular

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