Create Offer with Ashby API on New Presentation (Instant) from Google Drive API

Pipedream makes it easy to connect APIs for Ashby, Google Drive and 3,000+ other apps remarkably fast.

Trigger workflow on

New Presentation (Instant) from the Google Drive API

Next, do this

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

Select this integration
Configure the New Presentation (Instant) trigger
1. Connect your Google Drive account
2. Select a Drive
3. Configure Push notification renewal schedule
4. Configure alert
5. Optional- Select one or more Folders
Configure the Create Offer action
1. Connect your Ashby account
2. Configure Offer Process ID
3. Configure Offer Form ID
4. Configure Field Submissions
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 Presentation (Instant) on Google Drive

Description:Emit new event each time a new presentation is created in a drive.

Version:0.0.4

Key:google_slides-new-presentation

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 newFilesInstant from "../../../google_drive/sources/new-files-instant/new-files-instant.mjs";

export default {
  ...newFilesInstant,
  key: "google_slides-new-presentation",
  type: "source",
  name: "New Presentation (Instant)",
  description: "Emit new event each time a new presentation is created in a drive.",
  version: "0.0.4",
  hooks: {
    ...newFilesInstant.hooks,
    async deploy() {
      // Emit sample records on the first run
      const slides = await this.getPresentations(5);
      for (const fileInfo of slides) {
        const createdTime = Date.parse(fileInfo.createdTime);
        this.$emit(fileInfo, {
          summary: `New File: ${fileInfo.name}`,
          id: fileInfo.id,
          ts: createdTime,
        });
      }
    },
  },
  props: {
    ...newFilesInstant.props,
    folders: {
      ...newFilesInstant.props.folders,
      description:
        "(Optional) The folders you want to watch. Leave blank to watch for any new presentation in the Drive.",
    },
  },
  methods: {
    ...newFilesInstant.methods,
    shouldProcess(file) {
      return (
        file.mimeType.includes("presentation") &&
        newFilesInstant.methods.shouldProcess.bind(this)(file)
      );
    },
    getPresentationsFromFolderOpts(folderId) {
      const mimeQuery = "mimeType = 'application/vnd.google-apps.presentation'";
      let opts = {
        q: `${mimeQuery} and parents in '${folderId}' and trashed = false`,
      };
      if (!this.isMyDrive()) {
        opts = {
          corpora: "drive",
          driveId: this.getDriveId(),
          includeItemsFromAllDrives: true,
          supportsAllDrives: true,
          ...opts,
        };
      }
      return opts;
    },
    async getPresentations(limit) {
      const slides = [];
      const foldersIds = this.folders;
      for (const folderId of foldersIds) {
        const opts = this.getPresentationsFromFolderOpts(folderId);
        const filesWrapper = await this.googleDrive.listFilesInPage(null, opts);
        for (const file of filesWrapper.files) {
          const fileInfo = await this.googleDrive.getFile(file.id);
          slides.push(fileInfo);
          if (slides.length >= limit) { return slides; }
        }
      }
      return slides;
    },
  },
};

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`	Select a value from the drop down menu.
Folders	`folders`	`string[]`	Select a value from the drop down menu.

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#

Create Offer on Ashby

Description:Creates a new offer. [See the documentation](https://developers.ashbyhq.com/reference/offercreate)

Version:0.0.1

Key:ashby-create-offer

View on GitHub

Action Code#

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

export default {
  key: "ashby-create-offer",
  name: "Create Offer",
  description: "Creates a new offer. [See the documentation](https://developers.ashbyhq.com/reference/offercreate)",
  version: "0.0.1",
  type: "action",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: false,
  },
  props: {
    app,
    offerProcessId: {
      propDefinition: [
        app,
        "offerProcessId",
      ],
    },
    offerFormId: {
      type: "string",
      label: "Offer Form ID",
      description: "The ID of the form associated with the offer. The ID is included in the response of the [offer.start API](https://developers.ashbyhq.com/reference/offerstart).",
    },
    fieldSubmissions: {
      type: "string[]",
      label: "Field Submissions",
      description: `Array of field submission objects. Each object should contain:
- **path** (string, required): The form field's "path" value
- **value** (string, required): The field value (can be a primitive or complex type depending on field type)

You can find these referebce values in the response of the [offer.start API](https://developers.ashbyhq.com/reference/offerstart).

Each item can be a JSON string or object with the structure:
\`\`\`json
[
  {
    "path": "96377e55-cd34-49e2-aff0-5870ec102360",
    "value": "2025-11-07"
  },
  {
    "path": "ded2358d-443f-484f-91fa-ec7a13de842b",
    "value": {
      "value": 10000,
      "currencyCode": "USD"
    }
  }
]
\`\`\``,
    },
  },
  async run({ $ }) {
    const {
      app,
      offerProcessId,
      offerFormId,
      fieldSubmissions,
    } = this;

    const response = await app.createOffer({
      $,
      data: {
        offerProcessId,
        offerFormId,
        offerForm: {
          fieldSubmissions: utils.parseJson(fieldSubmissions),
        },
      },
    });

    $.export("$summary", `Successfully created offer for process ${offerProcessId}`);

    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
Ashby	`app`	`app`	This component uses the Ashby app.
Offer Process ID	`offerProcessId`	`string`	The ID of the offer process associated with the offer you're creating. This ID is included in the response of the offerProcess.start API
Offer Form ID	`offerFormId`	`string`	The ID of the form associated with the offer. The ID is included in the response of the offer.start API
Field Submissions	`fieldSubmissions`	`string[]`	Array of field submission objects. Each object should contain: path (string, required): The form field's "path" value value (string, required): The field value (can be a primitive or complex type depending on field type) You can find these referebce values in the response of the offer.start API Each item can be a JSON string or object with the structure: `[ { "path": "96377e55-cd34-49e2-aff0-5870ec102360", "value": "2025-11-07" }, { "path": "ded2358d-443f-484f-91fa-ec7a13de842b", "value": { "value": 10000, "currencyCode": "USD" } } ]`

Action Authentication#

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

About Ashby#

All-in-one Recruiting Software for Ambitious Teams

More Ways to Connect Ashby + Google Drive#

Other Popular Integrations#

Create Application with Ashby API on New Presentation (Instant) from Google Drive API

Google Drive + Ashby

Create Offer with Ashby API on New Presentation (Instant) from Google Drive API

Pipedream makes it easy to connect APIs for Ashby, Google Drive and 3,000+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of3,000+apps by most popular

1
-
24
of
3,000+
apps by most popular