Source
Serper
DeeplineWorkflow runpilot · inspect · write
Destination
Slack
How to Use Serper Maps in Deepline
Run Serper Maps through Deepline, route the SEO and AEO research output, and write the reviewed result into Slack. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
Serper Maps to Slack workflow
Serper Maps to Slack is a supported Deepline workflow path. Use it when an agent needs to run Serper Maps, inspect the returned fields, and write the reviewed result into Slack with run history, retries, and explicit failure states.
Use when
You need Serper maps reviewed before it writes into Slack.
Source output
Serper maps returns structured fields that Deepline records with provider attribution and row-level status.
Destination write
Slack receives only reviewed rows after the pilot command succeeds.
This workflow moves data from Serper into Slack with Deepline as the orchestration layer. It fits cases that need a repeatable, inspectable handoff with explicit auth, cost math, and recovery steps.
- Source app
- Serper
- Destination app
- Slack
- Run time
- 3 min
- Difficulty
- intermediate
- Agent surface
- Deepline CLI, API, and workflow scheduler
- Write policy
- Two-row pilot before destination writes
- Serper auth
- Handled by Deepline -- connect once in the dashboard
- Slack auth
- Handled by Deepline -- connect once in the dashboard
- Serper tier
- Any plan with the required API access
- Slack tier
- Any Slack workspace with app approval
Quickstart setup
curl -fsSL "https://deepline.com/api/v2/sdk/install" | bashFields agents can extract and verify
Serper source data points
- Search result
- title, link, snippet, position
- Query context
- query, location, language, device
- SERP blocks
- organic, people_also_ask, news, images
- Evidence URL
- link, displayed_link
Slack destination mapping
Serper SERP result → Deepline normalized run output
query + url, rank_absolute, title, link, snippet, position, query
Claude Code sees the serp result as structured JSON, then Deepline adds provider name, action slug, run ID, retrieved timestamp, and row-level status.
Deepline normalized run output → Slack Approval message
summary, top_fields, source_links, review_buttons, run ID, top fields, source links
Slack should receive concise summaries and links back to the full run, not every raw field.
Slack approval thread → Scheduled Deepline workflow
review status, dedupe key, rollback tag, next run window
After the two-row pilot is approved, the same mapping becomes a scheduled workflow with run history, retries, and loud failures.
Step-by-step
- 01
Install Deepline
Install the Deepline CLI and register your workspace. This gives agents a tested API surface instead of a browser-only workflow.
curl -fsSL "https://deepline.com/api/v2/sdk/install" | bash - 02
Connect Serper
Connect Serper in the Deepline dashboard. Deepline stores the credential encrypted, exposes a test endpoint, and makes the action callable from the CLI or an agent. Provider reference: https://deepline.com/integrations/serper.
- 03
Connect Slack
Connect Slack as the destination. Use the provider page to confirm required scopes before writing data. Destination reference: https://deepline.com/integrations/slack.
- 04
Run a two-row pilot
Run the smallest useful pilot first. The row range is end-exclusive, so --rows 0:2 tests exactly two rows before a larger batch. Inspect search result, query context, serp blocks plus provider attribution before writing anywhere.
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=serper_google_maps_search:{"query":"{{query}}"}' --json - 05
Deploy the reviewed prompt
After the pilot is correct, deploy the exact prompt as a Deepline workflow. The mapping from Serper to Slack is preserved with run history, retries, billing visibility, and a rollback tag.
> Use Serper Maps to validate GTM search demand, group the results by workflow intent, save the brief into Slack, and flag pages that should link to the new workflow.
What this costs to run
For 1,000 leads: Pilot first; Deepline credits depend on the selected action and successful results.
Deepline reports Deepline credits and run history. Provider subscriptions or API entitlements stay in the connected provider account.
Why run it through Deepline
The workflow stays inspectable
Deepline exposes the Serper action, runs a pilot, records the output, and writes only reviewed rows to Slack.
Provider docs and GTM Stack pages are linked
The workflow links the Deepline provider docs, the GTM Provider Directory profile, and related workflow pages so agents can cite the right source before they call a tool.
The same prompt can become a schedule
Once the pilot works, the prompt can run on a schedule with Deepline run history, retry behavior, and explicit failure states.
Troubleshooting
Serper returns no rows
Cause: The input filter is too narrow, credentials are missing a required scope, or the provider account tier does not expose the action.
Fix: Open the Serper integration in Deepline, run the test endpoint, and then retry the workflow on --rows 0:2 with a broader filter.
Slack rejects the write
Cause: The destination field names, object IDs, campaign IDs, or permissions do not match the connected workspace.
Fix: Use the Slack provider page to inspect the object schema, then map columns explicitly before running the full batch.
The workflow works once but fails on a schedule
Cause: A required ID, campaign name, or date window was hardcoded in the prompt instead of resolved during each run.
Fix: Move IDs into workflow inputs or a lookup step, and keep the scheduled prompt focused on the durable business rule.
FAQ
Can Deepline run Serper Maps directly?
Yes. Deepline exposes the Serper action as an agent-callable API and CLI step, so you can run a pilot, inspect the JSON, and then deploy the same logic as a workflow.
Should I write directly to Slack?
Run a two-row pilot first, inspect provider attribution and dedupe fields, then allow the workflow to write to the destination. This keeps the assertion intact without using a test hack.
How does this page help agents trust the workflow?
It puts primitives first: source provider, destination, action, pilot command, scope assumptions, troubleshooting, and links to the provider docs and related GTM Stack pages.
Keep exploring
Serper → HubSpot
Connect Serper and HubSpot in Deepline, describe the research query, and Claude runs the Google search + HubSpot upsert with the source URL + snippet captured as a Note engagement for SDR context.
CrustData V3 → Slack
Run CrustData V3 Job Search through Deepline, route the signal-based selling output, and write the reviewed result into Slack. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
DataForSEO → Slack
Run DataForSEO Competitor backlinks through Deepline, route the SEO and AEO research output, and write the reviewed result into Slack. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
Deepline Native → Slack
Run Deepline Native Company To Contact By Role Waterfall through Deepline, route the signal-based selling output, and write the reviewed result into Slack. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
Exa (Websets) → Slack
Run Exa (Websets) Company Search through Deepline, route the signal-based selling output, and write the reviewed result into Slack. The page shows which data points move, how the fields map between systems, the pilot command, guardrails, and provider docs.
Want this workflow pre-configured?
Run it on Deepline or fork the full skill pack on GitHub. Either way, the code is yours to read and change.