# Autom integrations: Google Search

> Autom is a search results API that returns Google, Bing and Brave results, news, images, maps and shopping listings as structured JSON for SEO and…

**Canonical page:** https://tray.ai/connectors/autom-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Autom is a search results API that returns Google, Bing and Brave results, news, images, maps and shopping listings as structured JSON for SEO and research work. Tray.ai connects to Autom through the HTTP Connector, so your workflows can call the Autom API alongside the rest of your stack.

## Use cases

### Google Search

Read google search in Autom from any Tray.ai workflow. The Autom API covers calls such as search Google and get search autocomplete.

- Search Google
- Get search autocomplete
- Search Google in AI Mode

### Google verticals

Read google verticals in Autom from any Tray.ai workflow. The Autom API covers calls such as search Google News and search Google Images.

- Search Google News
- Search Google Images
- Search Google Maps

### Bing and Brave

Read bing and brave in Autom from any Tray.ai workflow. The Autom API covers calls such as search Bing and search Brave.

- Search Bing
- Search Brave
- Search Brave images

### Account

Read account in Autom from any Tray.ai workflow. The Autom API covers calls such as get usage and credits and get an async job result.

- Get usage and credits
- Get an async job result

## Challenges Tray.ai solves

### Keeping Autom credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Autom credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Autom API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Autom API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Autom?

Yes. Tray.ai connects to Autom through the HTTP Connector, which calls the Autom API directly. Any call the Autom API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Autom?

The Autom API uses an API key in a request header and an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Autom connector?

Autom runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Autom connector from the Autom API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/