Skip to content
finn.
Integrations Google Cloud Run functions

Integration · Engineering and data

Google Cloud Run functions + Finn.

Google Cloud Run functions integration with Finn. Google Cloud Run functions runs code in response to web requests and cloud events.

Discuss this integration Explore the workflows

The work behind the connection

What you can do with Google Cloud Run functions.

Google Cloud Run functions runs code in response to web requests and cloud events.

Turn a website inquiry into a followed-up lead

Finn carries a submitted inquiry through your Cloud Run function into the sales process and completes the initial response.

Typically handled bySales development coordinator

Starts when

A website form submits a new business inquiry.

What Finn handles

  1. Read the submitted details and use the purpose-built intake function to apply the site's field mapping and submission checks.
  2. Match the person and company in connected HubSpot, then create or update the contact and inquiry record.
  3. Assign the accepted next step to the sales owner and send the inquiry confirmation through the team's email system.
  4. Record the response and follow-up task with the original submission reference.

The result

The inquiry becomes an accountable sales record with a completed first response and a scheduled next step.

Move an accepted order into operations

Finn uses your order-processing function to translate a commerce event into the records the fulfillment team needs.

Typically handled byOrder operations coordinator

Starts when

Shopify records an order accepted for the organization's fulfillment process.

What Finn handles

  1. Read the order event, customer details, line items, and fulfillment status.
  2. Invoke the purpose-built Cloud Run function that maps the order into the internal operations format.
  3. Create or update the corresponding order record through connected NetSuite and route any mapping exception to its data owner.
  4. Write the receiving-system reference back to the operational record and notify the fulfillment team that the order is ready.

The result

The accepted order is recorded in the operations system with its commerce reference and processing result.

Publish a supplier's accepted inventory update

Finn processes a supplier file through your function and updates the product availability used by the commerce team.

Typically handled byCommerce inventory coordinator

Starts when

A supplier uploads its current inventory file to the designated Cloud Storage location.

What Finn handles

  1. Read the file event and the accepted supplier-to-product mapping for the feed.
  2. Run the purpose-built function that transforms the supplier's quantities and identifies unmapped or invalid items.
  3. Apply the accepted inventory updates through connected Shopify, keeping physical stock decisions with the supplier's authoritative record.
  4. Record the products updated and request corrections for rejected rows, then send the import summary to operations.

The result

The commerce system reflects the accepted supplier feed and the import record identifies every unresolved item.

Complete a custom service request

Finn connects an employee's request to your internal application function and carries the result back to the service desk.

Typically handled byInternal applications administrator

Starts when

An employee requests a defined action that your internal software exposes through a function.

What Finn handles

  1. Read the employee request, the target business record, and the action's required inputs.
  2. Collect any required business-owner decision and call the purpose-built Cloud Run function for that action.
  3. Read the function's completed business result and resolve a missing-input exception with the requester.
  4. Update connected Freshservice with the changed record and send the employee the completed outcome.

The result

The internal system's action and the service request have matching completion records.

Load a partner file into the reporting dataset

Finn processes a submitted data file, follows its import, and completes the partner's data delivery record.

Typically handled byPartner data operations analyst

Starts when

A partner drops the recurring data file into Cloud Storage.

What Finn handles

  1. Read the source file, reporting period, and agreed data contract for the partner.
  2. Use the purpose-built Cloud Run function to transform the file and separate rejected records from accepted data.
  3. Send the accepted output to the connected Snowflake load process and read its actual import result.
  4. Publish the delivery summary in Google Drive and request corrections for unresolved records through the partner's email conversation.

The result

The reporting dataset contains the accepted partner delivery with its source file, load result, and exceptions documented.

Deliver a scheduled business report

Finn runs your Cloud Run reporting function, explains its output, and delivers the report where the business team works.

Typically handled byBusiness reporting coordinator

Starts when

Cloud Scheduler or a manager's request starts the recurring reporting job.

What Finn handles

  1. Read the report definition, reporting period, and intended audience.
  2. Invoke the purpose-built reporting function and collect its completed output, source dates, and data-quality notes.
  3. Turn the result into the agreed business report and save it through connected Google Drive.
  4. Send the report through the team's email system and update the recurring reporting task with its file and completion result.

The result

The business team receives the completed report with a clear reporting period and traceable source output.

Connection setup

Set up the connection around your work.

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Google Cloud Run functions.

Visit Google Cloud Run functions

The Finn platform

Finn Agents

Help customers. Work with your team. Finish the job.

Explore Agents

Finn Systems

Business apps for the work behind the conversation.

Explore Systems

Finn AI Gateway

Control connected AI apps, models, access, and spending.

Explore AI Gateway

Meet Finn

Put your Google Cloud Run functions integration to work.

Tell us which records, actions, and teams the connection needs to support.

Discuss your workflow Get started