> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/autom.md).

# Autom

https\://app.autom.dev

The Autom connector (*Find Google Results*, *Find Google News*, *Get Usage*, *Make API Call*) authenticates with an Autom API key. Each user enters their own key when they connect an account in the Designer, so you do not need to register an app with Autom.

Autom is a SERP API: it runs live Google searches and returns the results as JSON. *Find Google Results* returns the organic results of the first Google results page, *Find Google News* the articles of the first Google News page, *Get Usage* reads the credits of the connected account, and *Make API Call* reaches any other Autom endpoint at `https://api.autom.dev`.

## Get an API key

1. Sign up or sign in at [app.autom.dev](https://app.autom.dev). New accounts get free trial requests, no credit card needed.
2. Copy your API key from the dashboard.
3. In the Appmixer Designer, connect an Autom account and paste the key into the *API Key* field.

Appmixer checks the key with `GET https://api.autom.dev/v1/usage`, which uses no credits. Autom has no profile endpoint, so the connection is labelled with the masked key (for example `a1b2c3d4...wxyz`).

{% hint style="warning" %}
Treat the API key like a password. Anyone who has it can run searches that use the credits of your Autom account.
{% endhint %}

## Credits and limits

* *Find Google Results* and *Find Google News* use 1 credit per request. *Get Usage* is free.
* Credits are bought in packs and stay valid for one year. See [Autom pricing](https://autom.dev/pricing) for the current prices.
* Autom plans allow 50 to 300 requests per second. The connector queues requests at 600 per minute per user.

Use *Get Usage* in a flow to watch the remaining credits and the renewal date.

## Searching

* **Query** accepts Google search operators, for example `site:appmixer.com` or a phrase in quotes.
* **Country** is the 2-letter country code the results come from (`us` by default). **Language** is an optional language code such as `en` or `fr`.
* **Output Type** decides how the results leave the component: the whole list at once, the first result only, one result at a time, or a CSV file.
* When the search returns no result with a link, the component sends the query to its *Not Found* port instead, so the flow can branch on an empty result.

## Make API Call

*Make API Call* takes a path relative to `https://api.autom.dev`, for example `/v1/usage`. A full URL is accepted only when it points at `https://api.autom.dev`. Any other host is refused, so the API key is never sent elsewhere. The key is added to every request in the `x-api-key` header, and an `x-api-key` or `Authorization` header entered by the user is dropped.

## Troubleshooting

* **"Invalid Autom API key."** when connecting: the key is wrong or was deleted. Copy it again from the dashboard.
* **"Autom: ..."** errors: the message comes from the Autom API, for example no credits left. Check the remaining credits with *Get Usage*.
* **Nothing comes out of the&#x20;*****Out*****&#x20;port**: the search had no result, so the query went to the *Not Found* port. Connect it, or try a broader query or another country.

## Backoffice configuration

No Backoffice configuration is required. The connector reads one optional key.

Configuration ID: `appmixer:autom` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `outputFilePrefix` – optional. File name prefix of the CSV file that *Find Google Results* and *Find Google News* create when *Output Type* is set to a file; the file is named `<prefix>-<component name>.csv`. Default: `autom-objects-export`.

```bash
appmixer service-config set appmixer:autom -u -d '{
  "outputFilePrefix": "autom-objects-export"
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/autom.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
