Create Note with Cloze API on New Lead Form Entry from Google Ads API

Pipedream makes it easy to connect APIs for Cloze, Google Ads and 2,700+ other apps remarkably fast.

Trigger workflow on

New Lead Form Entry from the Google Ads API

Next, do this

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

Select this integration
Configure the New Lead Form Entry trigger
1. Connect your Google Ads account
2. Select a Use Google Ads As
3. Optional- Select a Managed Account
4. Configure timer
5. Select a Lead Form ID
6. Configure docsAlert
Configure the Create Note action
1. Connect your Cloze account
2. Configure Unique ID
3. Configure Source
4. Optional- Configure Date
5. Optional- Configure From
6. Optional- Configure Subject
7. Configure Body
8. Optional- Configure Additional Data
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 Lead Form Entry on Google Ads

Description:Emit new event for new leads on a Lead Form. [See the documentation](https://developers.google.com/google-ads/api/fields/v18/lead_form_submission_data)

Version:0.0.4

Key:google_ads-new-lead-form-entry

View on GitHub

Google Ads Overview#

The Google Ads API lets you programmatically manage your Google Ads data and
campaigns. You can use the API to automate common tasks, such as:

Creating and managing campaigns
Adding and removing keywords
Adjusting bids

You can also use the API to get information about your campaigns, such as:

Campaign stats
Keyword stats
Ad performance

The Google Ads API is a powerful tool that lets you manage your Google Ads data
and campaigns programmatically. With the API, you can automate common tasks,
such as creating and managing campaigns, adding and removing keywords, and
adjusting bids. You can also use the API to get information about your
campaigns, such as campaign stats, keyword stats, and ad performance.

Customizing API requests from within the Pipedream workflow builder

The Pipedream components interact with Google Ads API through an interal proxy service, which protects Pipedream's developer token.

The component accepts a standard Google Ads API request object with the following structure:

const googleAdsReq = {
  method: "get|post|put|delete", // HTTP method
  url: "/v18/...", // Google Ads API endpoint path
  headers: {
    Authorization: `Bearer ${this.googleAds.$auth.oauth_access_token}`,
  },
  data: {}, // Optional request body for POST/PUT requests
};

To make different API calls while using the proxy:

Modify the url path to match your desired Google Ads API endpoint
Update the method to match the required HTTP method
Add any necessary request body data in the data field
Include any required headers (Authorization is automatically included)

Example for a custom query:

const googleAdsReq = {
  method: "post",
  url: "/v16/customers/1234567890/googleAds:search",
  headers: {
    Authorization: `Bearer ${this.googleAds.$auth.oauth_access_token}`,
  },
  data: {
    query: "SELECT campaign.id, campaign.name FROM campaign",
  },
};

The proxy endpoint will remain the same: https://googleads.m.pipedream.net

Using Google Ads with the Connect API Proxy

To interface with Google Ads via the Connect API Proxy, you need to nest the request like this:

Important notes:

The upstream URL in this case is Pipedream's proxy service for Google Ads: https://googleads.m.pipedream.net
Like in the above examples, you'll define the Google Ads URL with the url param in the body
The method to the Connect Proxy should always be a POST, since it's actually targeting the Google Ads proxy (you can define the method for the Google Ads request in options.body.method)

Using the Pipedream SDK

const pd = createBackendClient({
  apiHost: process.env.API_HOST,
  credentials: {
    clientId: process.env.CLIENT_ID,
    clientSecret: process.env.CLIENT_SECRET,
  },
  environment: process.env.ENVIRONMENT,
  projectId: process.env.PROJECT_ID,
});

const pdGoogleAdsUrl = "https://googleads.m.pipedream.net";

const resp = await pd.makeProxyRequest(
  {
    searchParams: {
      external_user_id: process.env.EXTERNAL_USER_ID,
      account_id: process.env.ACCOUNT_ID,
    },
  },
  {
    url: pdGoogleAdsUrl,
    options: {
      method: "POST",
      body: {
        url: "/v19/customers:listAccessibleCustomers",
        method: "GET",
        // data: {} // If you need to send a body with a POST request, define it here
      },
    },
  }
);

Using the Connect REST API

Remember to use the Base64 encoded Pipedream endpoint for Google Ads: https://googleads.m.pipedream.net

curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/proxy/{url_safe_base64_encoded_url}?external_user_id={external_user_id}&account_id={apn_xxxxxxx}" \
  -H "Authorization: Bearer {access_token}" \
  -H "x-pd-environment: {development | production}" \
  -d '{
    "url": "/v19/customers:listAccessibleCustomers",
    "method": "GET",
    # "data": {} # If you need to send a body with a POST request, define it here
  }'

Trigger Code#

import common from "../common/common.mjs";
import sampleEmit from "./test-event.mjs";

const { googleAds } = common.props;

export default {
  ...common,
  key: "google_ads-new-lead-form-entry",
  name: "New Lead Form Entry",
  description: "Emit new event for new leads on a Lead Form. [See the documentation](https://developers.google.com/google-ads/api/fields/v18/lead_form_submission_data)",
  version: "0.0.4",
  type: "source",
  dedupe: "unique",
  sampleEmit,
  props: {
    ...common.props,
    leadFormId: {
      propDefinition: [
        googleAds,
        "leadFormId",
        (({
          accountId, customerClientId,
        }) => ({
          accountId,
          customerClientId,
        })),
      ],
    },
    docsAlert: {
      type: "alert",
      alertType: "info",
      content: "If needed, see Google's documentation on [submission fields](https://developers.google.com/google-ads/api/reference/rpc/v18/LeadFormSubmissionField) and [custom submission fields](https://developers.google.com/google-ads/api/reference/rpc/v18/CustomLeadFormSubmissionField).",
    },
  },
  methods: {
    ...common.methods,
    getSummary() {
      return "New Lead";
    },
    getItems() {
      const {
        accountId, customerClientId, leadFormId,
      } = this;
      return this.googleAds.getLeadFormData({
        accountId,
        customerClientId,
        leadFormId,
      });
    },
  },
};

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 Ads	`googleAds`	`app`	This component uses the Google Ads app.
Use Google Ads As	`accountId`	`string`	Select a value from the drop down menu.
Managed Account	`customerClientId`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Lead Form ID	`leadFormId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

Google Ads uses OAuth authentication. When you connect your Google Ads account, Pipedream will open a popup window where you can sign into Google Ads 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 Ads API.

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

emailprofilehttps://www.googleapis.com/auth/adwords

About Google Ads#

Reach customers wherever they are. Show up at the right time and place across the vast Google Ads ecosystem.

Action#

Create Note on Cloze

Description:Creates a note in Cloze. [See the documentation](https://api.cloze.com/api-docs/#!/Content/post_v1_createcontent).

Version:0.0.1

Key:cloze-create-note

View on GitHub

Cloze Overview#

The Cloze API enables you to access and manage your Cloze CRM data programmatically. In Pipedream, you can create powerful, serverless workflows that react to events or run on schedules to automate tasks involving Cloze data. You could synchronize contacts, track communication history, or trigger actions based on updates in Cloze. By leveraging Pipedream's capacity to connect to a myriad of services, you can create multi-step workflows that involve other apps to streamline your business processes and harness the full potential of CRM automation.

Action Code#

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

export default {
  key: "cloze-create-note",
  name: "Create Note",
  description: "Creates a note in Cloze. [See the documentation](https://api.cloze.com/api-docs/#!/Content/post_v1_createcontent).",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    uniqueId: {
      type: "string",
      label: "Unique ID",
      description: "A unique identifier for this content record. This will often be the unique Id in an external system so that updates can be matched up with the record in Cloze.",
    },
    source: {
      type: "string",
      label: "Source",
      description: "The source that this content record originally came from (Eg. `todoist.com`). Must be a valid domain.",
    },
    date: {
      type: "string",
      label: "Date",
      description: "When the content should show up in the timeline. Can be a string or a UTC timestamp in ms since the epoch. Eg. `2021-01-01` or `1609459200000`.",
      optional: true,
    },
    from: {
      type: "string",
      label: "From",
      description: "From address for this content record (the address of the person created the record). This can be an email address, phone number, social handle or app link (Eg. `na16.salesforce.com:006j000000Pkp1d`)",
      optional: true,
    },
    subject: {
      type: "string",
      label: "Subject",
      description: "Subject of the communication record.",
      optional: true,
    },
    body: {
      type: "string",
      label: "Body",
      description: "Body text of the communication record.",
    },
    additionalData: {
      type: "object",
      label: "Additional Data",
      description: "Additional details for the note in JSON format. [See the documentation](https://api.cloze.com/api-docs/#!/Content/post_v1_createcontent).",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      app,
      uniqueId,
      date,
      from,
      source,
      subject,
      body,
      additionalData,
    } = this;

    const response = await app.addContentRecord({
      $,
      data: {
        uniqueid: uniqueId,
        date,
        style: "note",
        from,
        source,
        subject,
        body,
        ...additionalData,
      },
    });

    $.export("$summary", "Successfully created note.");

    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
Cloze	`app`	`app`	This component uses the Cloze app.
Unique ID	`uniqueId`	`string`	A unique identifier for this content record. This will often be the unique Id in an external system so that updates can be matched up with the record in Cloze.
Source	`source`	`string`	The source that this content record originally came from (Eg. `todoist.com`). Must be a valid domain.
Date	`date`	`string`	When the content should show up in the timeline. Can be a string or a UTC timestamp in ms since the epoch. Eg. `2021-01-01` or `1609459200000`.
From	`from`	`string`	From address for this content record (the address of the person created the record). This can be an email address, phone number, social handle or app link (Eg. `na16.salesforce.com:006j000000Pkp1d`)
Subject	`subject`	`string`	Subject of the communication record.
Body	`body`	`string`	Body text of the communication record.
Additional Data	`additionalData`	`object`	Additional details for the note in JSON format. See the documentation

Action Authentication#

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