KindgiSign In
GuidesProviding Specific Details
Getting Started

Providing Specific Details

The single biggest factor in whether your agent works on the first try is how specific your prompt is. This guide shows you exactly what details to include for each app — Google Sheet headers, email filters, Trello board names, Slack channels — and proves the difference with a real example.

1Why Specifics Matter1/8
Phase 1Why details matter and how to think about them
01

Why Specifics Matter

When you create an agent, your prompt is the only context Kindgi has. It doesn't know your sheet layout, your board structure, or which emails matter. Every detail you leave out is a detail the agent has to guess — and guesses lead to mismatched columns, wrong emails processed, and cards landing in the wrong list.

Vague prompt
"Put order data into my Google Sheet and make a Trello card" — which columns? Which board? Which list? What data goes where?
Specific prompt
"Insert into my Google Sheet with headers: Order Number, Customer Name, Status. Create a card on my 'Orders' board in the 'Incoming' list"
Result: guesswork
Agent invents its own column names, picks a random Trello list, or misses emails entirely. You spend time fixing.
Result: first-try accuracy
Agent maps every field to the right column, creates cards in the right list, and updates the correct status.

Think of it this way: if you handed this task to a new colleague on their first day, what would they need to know to do it without asking a single question? That's the level of detail your prompt needs.

02

What Counts as a "Specific Detail"

Every connected app has key details that the agent needs to work correctly. These fall into four categories — and missing any one of them can cause problems.

Where to read from
Which app, which filter, which folder or label — tells the agent where data comes from
What the data looks like
Column headers, field names, data format — tells the agent how data is structured
Where to write to
Board name, list name, channel, sheet tab — tells the agent where results should go
What to update
Status values, labels, flags — tells the agent how to mark work as done

The next steps break down what these details look like for each app you might connect.

Phase 2What to include for each connected service
03

Google Sheets: Always List Your Headers

This is the single most impactful detail you can include. When your agent writes to a Google Sheet, it needs to know exactly which columns exist and in what order. Without headers, the agent invents its own column names — and they almost never match your actual sheet.

Without headers
"Add the order info to my sheet" — agent creates columns like 'order_id', 'customer', 'amount' that don't match your layout
With headers
"The sheet headers are: Order Number, Order Date, Customer Name, Customer Email, Item Name, Item Price, Quantity, Total Amount, Shipping address, Status" — perfect mapping
Google Sheets details to include
Column headers in the exact order they appear in your sheet
Sheet or tab name if your spreadsheet has multiple tabs
Where to insert — top of the sheet, bottom, or a specific range
Which rows to read — a filter condition like "where Status is 'Pending'"
Status value to write back when done — e.g. "update Status to 'Processed'"

Open your sheet, copy the header row, and paste it directly into your prompt. It takes five seconds and saves you from rearranging columns later.

04

Email: Name the Filter

When your agent reads email, it needs to know which messages to look for. A Gmail inbox can have thousands of emails — without a filter, the agent either processes too many or picks the wrong ones entirely.

Too broad
"Read my emails" — all of them? From today? From this year? The agent can't tell which ones matter.
Just right
"Find emails with 'Etsy Order Confirmation for:' in the subject line" — targets exactly the right messages
Email details to include
Subject line pattern or keywords to filter by
Sender address or domain if you know it
Label or folder if emails are pre-sorted
Time range — "from the last 24 hours" or "since last run"
What to extract — order numbers, names, amounts, links, attachments
05

Trello, Slack, and Other Destinations

Every destination app has its own structure. Trello has boards, lists, and cards. Slack has workspaces and channels. Google Calendar has calendars and event fields. Name the exact location where your data should land.

Trello
Board name, list name, card title format, what goes in the description
Slack
Channel name (#channel), message format, which fields to include
Google Calendar
Calendar name, event title format, duration, guests, description
Vague
"Create a Trello card with the details"
Specific
"Create a card on the 'Etsy Orders' board in the 'Incoming' list. Title: the customer name. Description: order number, items, total amount, and shipping address."
Vague
"Send a Slack notification"
Specific
"Post to #order-updates with the customer name, order total, and a link to the Trello card"

If your board, channel, or calendar has an unusual name, mention it exactly. "My 'Q1 Sprint Board'" is better than "my project board" — the agent matches the name you give it.

Phase 3A real prompt and the agent it produced
06

Real Example: One Prompt, Four Steps, Zero Guesswork

Here's a real prompt that uses every technique from this guide. It connects three apps (Gmail, Google Sheets, Trello), specifies exact filters, lists all ten sheet headers, and names the status value to write back.

Prompt

>Extract data from an incoming Etsy order emails - you can find them by looking for "Etsy Order Confirmation for: " in the subject line, drop it into a brand new row at the top of my Google Sheet, and then generate a new Trello card with all details, update the Google Sheet to show "entered". The sheet headers are: Order Number, Order Date, Customer Name, Customer Email, Item Name, Item Price, Quantity, Total Amount, Shipping address, Status.

Let's break down why this prompt works:

Source filter
"Look for 'Etsy Order Confirmation for:' in the subject line" — tells the agent exactly which emails to read
Sheet headers
All 10 columns listed in order — the agent maps each extracted field to the exact column
Insert position
"Brand new row at the top" — specifies where data goes, not just which sheet
Write-back value
"Update the Google Sheet to show 'entered'" — the exact status to set, no guessing
Every detail the agent needs — in a single prompt
07

The Agent Kindgi Built

From that single prompt, Kindgi created a precise 4-step workflow: fetch Etsy order confirmation emails from Gmail, extract order details from each email, insert new rows at the top of the Google Sheet mapped to all 10 headers, and create Trello cards with the full order details. Every step maps directly back to a detail in the prompt.

Step 1: Fetch emails
Filters Gmail by the exact subject line you specified
Step 2: Extract details
Pulls out the fields that match your 10 headers
Step 3.1: Insert rows
Writes to the sheet using your header mapping
Step 3.2: Create cards
Sends order details to your Trello board and list
Four clean steps — each one maps to a detail you provided
08

The Result: Correct Mapping on the First Run

On the first test run, the agent found 8 Etsy order confirmation emails, extracted all details, added 8 rows to the Google Sheet with every field in the correct column, and created 8 Trello cards in the right list. No manual cleanup. No mismatched columns. This is what happens when your prompt includes the right details.

8 emails found
Filtered by the exact subject line pattern
8 sheet rows
Each field mapped to the correct header column
8 Trello cards
Created in the specified list with full details

The difference between "it worked" and "I need to fix column mapping" is usually one line in your prompt: the list of headers. Spend 10 seconds copying them — save 10 minutes of cleanup.

8 orders processed perfectly — because every detail was specified upfront

You're all set

Your Providing Specific Details guide is complete.

Providing Specific Details Guide | Kindgi