HumDay

Updates the Business call settings for the specified location in Google My Business Business Calls

A documented Google My Business Business Calls operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Updates the Business call settings for the specified location.

  • PATCHChanges data · locationsmybusinessbusinesscalls.googleapis.com/v1/{name}

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google My Business Business Calls operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google My Business Business Calls operations

All 3 Google My Business Business Calls operations

Questions

Can HumDay updates the business call settings for the specified location in Google My Business Business Calls?
Yes. This operation is published in Google My Business Business Calls's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Will this change my Google My Business Business Calls data?
Yes — this is a PATCH operation, so it changes something in Google My Business Business Calls. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google My Business Business Calls account.

Where this came from

Read from a published API description for Google My Business Business Calls at mybusinessbusinesscalls.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.

We use cookies to measure how the site is used.