> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Adyntel in Deepline

> Use channel-native ad endpoints first, then synthesize cross-channel insights. Includes SDK V2 examples, input constraints, response fields, and Deepline cost.

[Human guide: work with your agent →](https://deepline.com/docs/human/providers/adyntel/guide.md)
Inspect one Adyntel action before starting provider-backed work. Your first result is a verified input and output contract.

## Provider-specific requirements

Use Adyntel for paid-media intelligence (creative examples, channel presence, and ad strategy signals).

* Deepline injects required Adyntel account identity fields automatically.
* Normalize domains to bare host format (`company.com`, no protocol or `www`).
* Use channel-native tools (`adyntel_facebook`, `adyntel_google`, `adyntel_linkedin`, `adyntel_tiktok_search`) before cross-channel synthesis.
* Prefer `adyntel_google_shopping_sync` to launch and poll Google Shopping in one call.
* Keep `adyntel_google_shopping_status` for manual follow-up polling when you already have an `id`.
* Use `adyntel_tiktok_ad_details` only after collecting IDs from `adyntel_tiktok_search`. pass `id` as a string.
* Billing is request-based for paid endpoints, so pre-filter targets before broad sweeps.

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute adyntel_google --payload '{"company_domain":"hubspot.com"}'
```

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute adyntel_google_shopping_sync --payload '{"company_domain":"allbirds.com"}'
```

## Find an applicable action

Confirm your effective workspace, then search the live catalog:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline auth status --json
deepline search "Adyntel" --type tools --json
```

Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

## Inspect the selected contract

Replace `<returned-tool-id>` with the identifier returned by discovery:

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline describe <returned-tool-id> --json
```

These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits.

A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

## Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept.

Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects.

For reusable logic, follow [Write Plays](https://deepline.com/docs/sdk-v2/plays.md). For direct-call recovery, use [Tool execution recovery](https://deepline.com/docs/sdk-v2/tool-execution-recovery.md).

> [!TIP]
>
> Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.