Upload File with Uploadcare API on New Row Created from Coda API

Pipedream makes it easy to connect APIs for Uploadcare, Coda and 2,400+ other apps remarkably fast.

Trigger workflow on

New Row Created from the Coda API

Next, do this

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

Select this integration
Configure the New Row Created trigger
1. Connect your Coda account
2. Configure timer
3. Select a Doc ID
4. Select a Table ID
5. Optional- Configure Include Updated Rows
Configure the Upload File action
1. Connect your Uploadcare account
2. Configure Source URL
3. Optional- Select a Store
4. Optional- Configure Check URL Duplicates
5. Optional- Configure Save URL Duplicates
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 Row Created on Coda

Description:Emit new event for every created / updated row in a table. [See the documentation.](https://coda.io/developers/apis/v1#tag/Rows/operation/listRows)

Version:0.0.4

Key:coda-row-created

View on GitHub

Coda Overview#

The Coda API enables you to interact with your Coda docs for both data retrieval and manipulation. By leveraging this API on Pipedream, you can automate document updates, synchronize data across different platforms, orchestrate complex workflows, and react to changes in real-time. Coda’s tables can act as dynamic databases that interconnect with various services, allowing you to streamline operations that depend on the timely and accurate exchange of information.

Trigger Code#

import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import coda from "../../coda.app.mjs";

export default {
  key: "coda-row-created",
  name: "New Row Created",
  description: "Emit new event for every created / updated row in a table. [See the documentation.](https://coda.io/developers/apis/v1#tag/Rows/operation/listRows)",
  type: "source",
  version: "0.0.4",
  dedupe: "unique",
  props: {
    coda,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    docId: {
      propDefinition: [
        coda,
        "docId",
      ],
    },
    tableId: {
      propDefinition: [
        coda,
        "tableId",
        (c) => ({
          docId: c.docId,
        }),
      ],
    },
    includeUpdates: {
      type: "boolean",
      label: "Include Updated Rows",
      description: "Emit events for updates on existing rows?",
      optional: true,
    },
  },
  hooks: {
    async deploy() {
      const rows = await this.fetchRows(25);
      this.emitEvents(rows.reverse());
    },
  },
  methods: {
    _getLastTs() {
      return this.db.get("lastTs") || 0;
    },
    _setLastTs(lastTs) {
      this.db.set("lastTs", lastTs);
    },
    getTsKey() {
      return this.includeUpdates
        ? "updatedAt"
        : "createdAt";
    },
    async fetchRows(maxResults) {
      const rows = [];
      const tsKey = this.getTsKey();
      const lastTs = this._getLastTs();
      let maxTs = lastTs;
      let done = false;

      const params = {
        sortBy: tsKey,
      };

      while (true) {
        const {
          items = [],
          nextPageToken,
        } = await this.coda.findRow(
          null,
          this.docId,
          this.tableId,
          params,
        );
        for (const item of items) {
          const ts = Date.parse(item[tsKey]);
          if (ts > lastTs) {
            rows.push(item);
            if (ts > maxTs) {
              maxTs = ts;
            }
            if (rows.length >= maxResults) {
              done = true;
              break;
            }
          }
          else {
            done = true;
          }
        }
        params.pageToken = nextPageToken;

        if (!nextPageToken || done) {
          this._setLastTs(maxTs);
          return rows;
        }
      }
    },
    rowSummary(row) {
      const name = row.name && ` - ${row.name}` || "";
      return `Row index: ${row.index}` + name;
    },
    emitEvents(events) {
      for (const row of events) {
        const id = this.includeUpdates
          ? `${row.id}-${row.updatedAt}`
          : row.id;

        this.$emit(row, {
          id,
          summary: this.rowSummary(row),
          ts: row.updatedAt,
        });
      }
    },
  },
  async run() {
    const rows = await this.fetchRows();
    this.emitEvents(rows.reverse());
  },
};

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
Coda	`coda`	`app`	This component uses the Coda app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Doc ID	`docId`	`string`	Select a value from the drop down menu.
Table ID	`tableId`	`string`	Select a value from the drop down menu.
Include Updated Rows	`includeUpdates`	`boolean`	Emit events for updates on existing rows?

Trigger Authentication#

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

About Coda#

Coda is familiar like a doc and engaging like an app, so your team can jump in quickly, collaborate effectively, and make decisions that stick.

Action#

Upload File on Uploadcare

Description:Upload a file. [See docs here](https://uploadcare.com/api-refs/upload-api/#operation/fromURLUpload)

Version:0.0.1

Key:uploadcare-upload-file

View on GitHub

Uploadcare Overview#

Uploadcare is a file uploading, processing, and delivery platform that provides developers with tools to handle the entire file lifecycle with ease. With its robust API, you can upload files from any device, transform images and documents on-the-fly, and manage digital content with a comprehensive set of features. Integrating Uploadcare with Pipedream allows you to craft workflows that automate file operations and connect them seamlessly with other services, such as CRMs, marketing platforms, and data analysis tools.

Action Code#

import uploadcare from "../../uploadcare.app.mjs";
import constants from "../common/constants.mjs";

export default {
  name: "Upload File",
  version: "0.0.1",
  key: "uploadcare-upload-file",
  description: "Upload a file. [See docs here](https://uploadcare.com/api-refs/upload-api/#operation/fromURLUpload)",
  type: "action",
  props: {
    uploadcare,
    sourceURL: {
      label: "Source URL",
      description: "Source URL of the file to fetch and upload",
      type: "string",
    },
    store: {
      label: "Store",
      description: "Determines if an uploaded file should be marked as temporary or permanent",
      type: "string",
      optional: true,
      options: constants.STORE_TYPES,
      default: "0",
    },
    checkURLDuplicates: {
      label: "Check URL Duplicates",
      description: "If the `Source URL` had already been fetched and uploaded previously, this request will return information about the already uploaded file.",
      type: "boolean",
      optional: true,
    },
    saveURLDuplicates: {
      label: "Save URL Duplicates",
      description: "Determines if the requested `Source URL` should be kept in the history of fetched/uploaded URLs. If the value is not defined explicitly, it is set to the value of the `Check URL Duplicates` parameter.",
      type: "boolean",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.uploadcare.uploadFileFromURL({
      $,
      data: {
        source_url: this.sourceURL,
        store: this.store,
        check_URL_duplicates: this.checkURLDuplicates,
        save_URL_duplicates: this.saveURLDuplicates,
      },
    });

    if (response) {
      $.export("$summary", `Successfully uploaded file with token ${response.token}`);
    }

    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
Uploadcare	`uploadcare`	`app`	This component uses the Uploadcare app.
Source URL	`sourceURL`	`string`	Source URL of the file to fetch and upload
Store	`store`	`string`	Select a value from the drop down menu:`{ "label": "Do not mark an uploaded file as stored and remove it after 24 hours", "value": "0" }{ "label": "mark the uploaded file as stored", "value": "1" }{ "label": "delegate the choice of the file storing behavior to a project-wide setting called auto-store.", "value": "auto" }`
Check URL Duplicates	`checkURLDuplicates`	`boolean`	If the `Source URL` had already been fetched and uploaded previously, this request will return information about the already uploaded file.
Save URL Duplicates	`saveURLDuplicates`	`boolean`	Determines if the requested `Source URL` should be kept in the history of fetched/uploaded URLs. If the value is not defined explicitly, it is set to the value of the `Check URL Duplicates` parameter.