Question 1

What is TrailMeta and how does it work?

Accepted Answer

TrailMeta is a web-based tool that connects to your Salesforce org, extracts all metadata (objects, fields, flows, Apex classes, triggers, LWC, profiles, permission sets, connected apps, named credentials, and installed packages), and produces structured markdown documentation optimized for AI platforms. You connect your org credentials, TrailMeta runs a 7-tier extraction pipeline across Salesforce REST, Tooling, and Metadata APIs, then outputs files you can feed directly to ChatGPT, Claude, Gemini, Cursor, Copilot, or any AI tool. No installation in your org is required.

Question 2

Which Salesforce editions does TrailMeta support?

Accepted Answer

TrailMeta works with any Salesforce edition that has API access enabled: Enterprise Edition, Unlimited Edition, Performance Edition, and Developer Edition. Professional Edition does not include API access by default — you would need the API Access add-on. Government Cloud (GovCloud) orgs are also supported as long as API access is available. Sandbox orgs (Developer, Developer Pro, Partial, Full) all work and are a great way to test TrailMeta before running it on production.

Question 3

What Salesforce permissions do I need to use TrailMeta?

Accepted Answer

You need a Salesforce user with the following permissions: API Enabled, View Setup and Configuration, and Modify All Data (for complete metadata access across all tiers). A System Administrator profile includes all of these by default. If you cannot use a full admin, a read-only admin profile works for most extraction tiers — you may miss some Metadata API components in Tier 4 (profiles and permission sets) without Modify All Data. TrailMeta never modifies your org; all API calls are read-only.

Question 4

How long does Salesforce metadata extraction take?

Accepted Answer

Extraction time depends on your org size. Small orgs (under 50 custom objects, fewer than 20 flows) typically complete in 2-5 minutes. Medium orgs (50-200 objects, 20-100 flows) take 5-15 minutes. Large enterprise orgs (200+ objects, 100+ flows, extensive Apex) may take 15-30 minutes. AI enrichment adds another 5-20 minutes depending on component count. You can watch real-time progress as each of the 7 tiers completes. Extraction is designed to respect Salesforce API rate limits so it will not impact your org performance.

Question 5

Should I run TrailMeta on a sandbox or production org?

Accepted Answer

Both work. If you want a complete picture of your production architecture — including all custom objects, flows, Apex, profiles, and integrations — run it on production. If you want to test TrailMeta first or only need the development environment's metadata, use a Full or Partial sandbox. Developer sandboxes work but only contain metadata, not data, which is fine for TrailMeta since it only reads metadata anyway. Many teams run TrailMeta on production first, then use the output to plan sandbox-based development with full org context.

Question 6

What exactly does TrailMeta extract from my Salesforce org?

Accepted Answer

TrailMeta runs a 7-tier extraction pipeline. Tier 1: Objects and fields (your complete data model with field types, relationships, picklist values, and formulas). Tier 2: Flows, Apex classes, triggers, and validation rules (all automation and business logic). Tier 3: Lightning Web Components. Tier 4: Profiles, permission sets, and permission set groups (your security model). Tier 5: Connected apps and named credentials (integrations). Tier 6: Installed packages and org summary. Tier 7 (optional): AI enrichment — two-pass analysis that adds org health reports, impact analysis, business process maps, and more. Every component includes cross-references showing how it relates to other components in your org.

Question 7

Does TrailMeta access my Salesforce records or customer data?

Accepted Answer

No. TrailMeta extracts metadata only — the structure and configuration of your org, not the data stored in it. It reads object definitions, field schemas, flow configurations, Apex source code, profile settings, and similar structural information. It never queries Account records, Contact records, Opportunity records, or any business data. No PII, no customer information, no transactional data is ever accessed, transmitted, or stored. The Salesforce APIs TrailMeta uses (Describe, Tooling API, Metadata API) return schema information, not record data.

Question 8

What export formats does TrailMeta offer?

Accepted Answer

TrailMeta produces 5 export formats optimized for different AI platforms: (1) Single File — everything in one markdown file with a table of contents, ideal for Claude chat, Gemini, or any AI chat interface. (2) Consolidated Pack — files merged by category into 20 or fewer files, designed for Claude Projects, ChatGPT Projects, Custom GPTs, and NotebookLM Free (which have file count limits). (3) Full Pack — individual files for every component plus a README, ideal for NotebookLM Pro, OpenAI File Search, LangChain, and LlamaIndex. (4) IDE Project — Full Pack plus pre-configured project files for Cursor, Claude Code, Copilot, Windsurf, and Codex. (5) API Bundle — Full Pack plus graph.json and metadata.json for developers building custom integrations.

Question 9

How does TrailMeta handle managed packages from the AppExchange?

Accepted Answer

Custom and unlocked package components are fully extracted — source code, flow definitions, field schemas, everything. For managed (first-generation) packages installed from the AppExchange, TrailMeta can extract object and field schemas but cannot access encrypted source code. This is a Salesforce platform limitation, not a TrailMeta limitation — Apex source, flow XML, LWC markup, and validation rule formulas in managed packages are encrypted and inaccessible to any external tool. You can optionally include or exclude managed package object schemas from your extraction.

Question 10

Can I re-run extraction after making changes to my org?

Accepted Answer

Yes. Each extraction is independent. If you make changes to your Salesforce org — add objects, modify flows, update Apex — you can run TrailMeta again to get an updated snapshot. Each run is a separate $15 extraction. There is no subscription and no ongoing cost. Many teams re-extract quarterly or before major projects (migrations, new feature builds, org audits) to ensure their AI tools have current context.

Question 11

How do I use TrailMeta output with ChatGPT?

Accepted Answer

For ChatGPT conversations: download the Single File format and paste it into your conversation, or attach it as a file. For ChatGPT Projects: download the Consolidated Pack (20 or fewer files) and upload all files to a project — ChatGPT will use them as persistent context across all conversations in that project. For Custom GPTs: upload the Consolidated Pack as knowledge files when configuring your GPT. For OpenAI File Search (Assistants API): use the Full Pack format. Each format is optimized for ChatGPT's specific file and context constraints. See our blog post "How to Feed Your Entire Salesforce Org to ChatGPT" for a step-by-step walkthrough.

Question 12

How do I use TrailMeta output with Claude?

Accepted Answer

For Claude conversations: use the Single File format — paste it or attach it as a file. Claude's 200K context window handles even large org exports well. For Claude Projects: upload the Consolidated Pack as project knowledge — Claude will reference it across all conversations in the project. For Claude Code (CLI): use the IDE Project format, which includes a pre-configured CLAUDE.md file that tells Claude Code about your org architecture, naming conventions, and key relationships. Drop the output folder into your SFDX project root and Claude Code immediately understands your org.

Question 13

How do I use TrailMeta output with Cursor IDE?

Accepted Answer

Download the IDE Project export format. It includes a .cursor/rules/salesforce-org.mdc file — Cursor's native rules format — pre-populated with your org's objects, fields, flows, Apex classes, naming conventions, and relationships. Place the TrailMeta output in your SFDX project root. When you open the project in Cursor, the AI assistant automatically loads your org context. You can then ask Cursor to write Apex that references your actual objects and fields, debug flows with full awareness of your automation chain, and generate test classes that match your real data model.

Question 14

How do I use TrailMeta output with Google Gemini or NotebookLM?

Accepted Answer

For Gemini conversations: use the Single File format — Gemini's large context window (1M+ tokens) handles it well. For NotebookLM Free: upload the Consolidated Pack (20 or fewer files) as sources. NotebookLM will index your entire org architecture and let you ask questions, generate summaries, and even create audio overviews of your Salesforce org. For NotebookLM Pro: use the Full Pack with individual files for more granular source attribution. Gemini and NotebookLM are particularly strong at summarizing complex org relationships and generating executive-level architecture overviews.

Question 15

How do I use TrailMeta output with GitHub Copilot?

Accepted Answer

Download the IDE Project export format. It includes a .github/copilot-instructions.md file pre-configured with your Salesforce org context — objects, fields, relationships, automation patterns, and naming conventions. Place this in your SFDX project root. GitHub Copilot reads copilot-instructions.md as workspace-level context, so every code suggestion it makes will be informed by your actual org architecture. This is especially useful for writing Apex triggers, test classes, and LWC components that need to reference your real custom objects and fields.

Question 16

What does TrailMeta AI enrichment actually do?

Accepted Answer

AI enrichment runs two analysis passes over your extracted metadata. Pass 1 (Component Intelligence): Each object, flow, Apex class, trigger, and profile is individually analyzed — complexity scoring, risk flags, dependency notes, and architecture observations. Pass 2 (Cross-Cutting Analysis): The enrichment engine generates new documents from the full org context: business process maps that trace end-to-end workflows, domain digests that group related components, impact analysis showing blast radius for changes, execution order documentation showing what fires when, an org health report identifying technical debt and risks, and a START HERE guide that tells AI consumers where to begin.

Question 17

How is AI enrichment pricing calculated?

Accepted Answer

AI enrichment cost is calculated transparently before you confirm. The formula: $15 base fee + (Gemini API processing cost x 1.54). The 1.54 multiplier covers infrastructure and margin. Typical totals by org size: small orgs (under 50 objects): ~$20 total. Medium orgs (50-200 objects): ~$25-35 total. Large orgs (200-500 objects): ~$40-60 total. Enterprise orgs (500+ objects): ~$60-100+ total. The exact cost is calculated and displayed based on your specific org's component count before you approve the charge. You always see the price before paying.

Question 18

Do I need AI enrichment or is extraction alone enough?

Accepted Answer

Extraction alone ($15) gives you complete, well-structured markdown documentation of your entire org — objects, fields, flows, Apex, triggers, profiles, permissions, integrations, and packages. This is enough for most use cases: feeding context to AI coding assistants, documenting your org for onboarding, or understanding your architecture. AI enrichment adds analysis on top: health reports, risk flags, business process maps, and cross-cutting insights. It is most valuable for org audits, migration planning, technical debt assessments, and when you want AI-generated architectural analysis rather than just raw documentation.

Question 19

How does TrailMeta protect my Salesforce metadata?

Accepted Answer

All extracted metadata is encrypted at rest using AES-256-GCM with per-job encryption keys. Data is transmitted over TLS 1.3. Each extraction job is isolated — your data is never mixed with other customers' data. Files are automatically and permanently deleted 48 hours after extraction. TrailMeta does not store your Salesforce credentials; OAuth tokens are used only during the active extraction session. No metadata is used for model training or shared with third parties. See our full Security Policy at /security for complete details.

Question 20

How are my Salesforce credentials handled?

Accepted Answer

TrailMeta uses Salesforce OAuth 2.0 for authentication — you authorize TrailMeta through Salesforce's standard login flow. Your username and password are never entered into or stored by TrailMeta. The OAuth access token is used only during the active extraction session and is not persisted after extraction completes. If you prefer, you can also connect using a Salesforce security token with username/password authentication, but OAuth is recommended as the more secure option.

Question 21

Is TrailMeta compliant with enterprise security requirements?

Accepted Answer

TrailMeta is designed with enterprise security in mind. Key controls: metadata-only extraction (no record data or PII), AES-256-GCM encryption at rest, TLS 1.3 in transit, per-job isolation, 48-hour automatic data deletion, no credential storage, and read-only API access (your org is never modified). TrailMeta does not require a connected app installed in your org, which simplifies security reviews. For organizations with strict data residency requirements, extracted data is processed and stored in US-based infrastructure.

Question 22

How much does TrailMeta cost? Is there a subscription?

Accepted Answer

TrailMeta uses simple, one-time pricing with no subscription. Extraction: $15 flat fee per extraction — you get complete metadata extraction across all 7 tiers with all 5 export formats included. AI Enrichment (optional): $15 base + AI processing cost based on your org size (typically $5-65 additional, calculated and shown before you confirm). There are no monthly fees, no per-user pricing, no contracts, and no hidden costs. You pay once per extraction. If you need to re-extract after org changes, each run is another $15.

Question 23

How does TrailMeta compare to Elements.cloud pricing?

Accepted Answer

Elements.cloud costs $495-995/month depending on your plan, with annual contracts. That is $5,940-11,940 per year. TrailMeta is $15 one-time per extraction. The products serve different purposes: Elements.cloud produces interactive documentation for human readers (dashboards, diagrams, wikis). TrailMeta produces structured markdown optimized for AI consumption. If your goal is to give AI tools (ChatGPT, Claude, Cursor, Copilot) complete context about your Salesforce org, TrailMeta is purpose-built for that at a fraction of the cost.

Question 24

How does TrailMeta compare to Hubbl Diagnostics?

Accepted Answer

Hubbl Diagnostics provides org health scoring and visual dashboards for Salesforce admins and architects. It is a human-facing analysis tool. TrailMeta produces AI-ready documentation — structured markdown that AI platforms can consume and reason about. If you need a dashboard to browse your org health in a browser, Hubbl is a good choice. If you need to feed your complete org architecture to Claude, ChatGPT, Cursor, or any AI coding tool so it understands your specific objects, flows, and Apex, TrailMeta is the tool for that.

Question 25

How do I use TrailMeta for a Salesforce org audit?

Accepted Answer

Run TrailMeta with AI enrichment enabled. The enrichment tier generates an Org Health Report that identifies technical debt, unused components, security gaps, overly complex automation, and architecture risks. The Impact Analysis documents show blast radius for potential changes. Business Process Maps trace end-to-end workflows so you can see where automation overlaps or conflicts. Upload the output to Claude or ChatGPT and ask specific audit questions: "What are the riskiest components in this org?" "Which flows have redundant logic?" "What objects have no automation but should?" The AI can reason about your entire org architecture at once.

Question 26

How do I use TrailMeta for Salesforce migration planning?

Accepted Answer

Extract your source org with TrailMeta, then feed the output to your AI tool of choice. The AI now understands your complete data model, all automation (flows, triggers, validation rules), security model (profiles, permission sets), and integrations. Ask it to help plan your migration: identify dependencies that must move together, flag components that reference hardcoded IDs, surface automation that may break if object relationships change, and generate a phased migration checklist. For org merges or splits, extract both orgs and feed both extractions to the AI to identify conflicts, overlaps, and compatibility issues.

Question 27

How do I use TrailMeta for developer onboarding?

Accepted Answer

New developers joining a Salesforce team face weeks of ramp-up time understanding the org architecture. TrailMeta shortens this dramatically. Extract your org, give the new developer the output files, and have them load it into their preferred AI tool. They can ask natural-language questions: "How does the opportunity-to-invoice flow work?" "What triggers fire on the Account object?" "Which profiles have access to the Revenue_Forecast__c object?" The AI becomes an always-available org expert that can explain any component, trace any dependency, and answer any architecture question instantly.

Question 28

What is vibe coding for Salesforce and how does TrailMeta help?

Accepted Answer

Vibe coding means using AI coding assistants (Cursor, Claude Code, Copilot, Windsurf) to write code through natural-language conversation rather than manual coding. The challenge with vibe coding Salesforce: your AI assistant does not know your org. It generates generic Apex referencing standard objects when you have custom objects. It writes triggers without knowing your existing automation chain. TrailMeta solves this by giving your AI coding assistant complete org context. With the IDE Project export, your AI knows your objects, fields, relationships, flows, triggers, and naming conventions — so it writes code that actually works in your org.

Question 29

How do I map Salesforce technical debt with AI?

Accepted Answer

Traditional technical debt discovery in Salesforce means clicking through Setup screens one component at a time. TrailMeta extracts everything at once, and the AI enrichment tier specifically identifies: unused custom objects and fields, flows with redundant or overlapping logic, Apex classes not referenced by any trigger or test, overly permissive profiles, validation rules that may conflict, and deprecated API versions in use. Feed the output to Claude or ChatGPT and ask for a prioritized technical debt remediation plan. The AI can see patterns across your entire org that would take a human weeks to discover manually.

Question 30

TrailMeta cannot connect to my Salesforce org. What should I check?

Accepted Answer

First, verify your credentials work by logging into Salesforce directly. Then check: (1) Your user has API Enabled permission — go to Setup > Users > your user > Profile and confirm. (2) Your org allows API access — some sandbox configurations restrict API access. (3) If using a custom domain (My Domain), ensure you are entering the correct login URL. (4) If your org uses IP restrictions, your current IP may need to be allowlisted in your Salesforce Login IP Ranges or Network Access settings. (5) Check if your org has active Connected App policies that block new OAuth connections. TrailMeta logs connection errors with specific Salesforce error codes to help diagnose the issue.

Question 31

My extraction seems to be missing some components. Why?

Accepted Answer

Common reasons: (1) Permission gaps — if your user does not have Modify All Data, some Metadata API components (particularly detailed profile and permission set data) may be inaccessible. (2) Managed packages — source code in managed packages is encrypted by Salesforce and cannot be extracted. You will see the object schemas but not Apex or flow definitions. (3) Recently created components — if you created components after starting extraction, they will not be included. Re-run extraction to pick them up. (4) Tooling API limits — very large orgs may hit Salesforce query limits during extraction. TrailMeta handles pagination automatically, but extremely large result sets may require multiple runs.

Question 32

Extraction is taking too long or timing out for my large org. What can I do?

Accepted Answer

Large enterprise orgs (500+ objects, hundreds of flows, extensive Apex) can take 30+ minutes. If extraction times out: (1) Check your browser has not gone to sleep — keep the tab active during extraction. (2) Try extracting during off-peak hours when Salesforce API response times are faster. (3) If specific tiers are slow, it is usually Tier 2 (flows and Apex — large orgs may have hundreds of each) or Tier 4 (profiles and permission sets — some orgs have 50+ profiles). The extraction engine respects Salesforce rate limits, so slower extraction means your org has a lot of metadata — which is exactly why you need TrailMeta.

Question 33

I entered my PIN wrong and now the page says "Unauthorized". What happened?

Accepted Answer

For your protection, we lock the PIN for 15 minutes after 5 failed attempts. This prevents anyone who intercepts your download link from brute-forcing the 6-digit PIN. Wait 15 minutes and try again with the correct PIN. If you have lost the PIN, you will need to re-run the extraction — PINs are generated fresh per job and are never stored anywhere we can retrieve them. All failure responses look identical on purpose, so an attacker cannot tell whether they got the PIN wrong, the token wrong, or guessed a non-existent job.

Question 34

Where do I find my PIN after extraction finishes?

Accepted Answer

The 6-digit PIN is shown on screen immediately after you connect your org — it appears on the same page where your download link is displayed. Save it somewhere safe before you close the tab. PINs are generated once per extraction job using a cryptographically secure random number generator, and we do not store them anywhere retrievable. If you lose the PIN, the fastest path is to re-run extraction (each run is a fresh $15 job with a new PIN and new download link).

Question 35

My download link stopped working. Why?

Accepted Answer

Download links expire after 48 hours and are capped at 5 successful downloads per job — whichever comes first. After either limit, the server permanently deletes the generated files and the link returns a 410 Gone. This is intentional: it minimizes the window during which a leaked link could be abused, and it keeps your metadata from sitting on our servers indefinitely. If you need to download again, re-run extraction to generate a new job with a fresh 48-hour window.

Question 36

TrailMeta rejected my Salesforce login URL with a 400 error. What URLs are allowed?

Accepted Answer

For security (to prevent the server being tricked into connecting to arbitrary hosts), TrailMeta only accepts three shapes of login URL: (1) https://login.salesforce.com — standard production login. (2) https://test.salesforce.com — sandbox login. (3) https://.my.salesforce.com — MyDomain URLs (including sandbox variants like --.sandbox.my.salesforce.com). URLs must use HTTPS, port 443, and no path/query/fragment. If your org uses Enhanced Domains (mandatory since Salesforce Winter '24), your MyDomain URL will work. If you are seeing this error with a legitimate MyDomain URL, double-check you copied it correctly from Setup > My Domain.

Question 37

I am getting "Too many requests" when trying to connect. What is going on?

Accepted Answer

The connect endpoint is rate-limited to 5 attempts per 15 minutes per IP address to block credential-stuffing attacks. If you triggered the limit by mistyping your password a few times, wait 15 minutes and try again. If you are behind a shared NAT (corporate network, VPN) and someone else on the same IP hit the limit, you may see this error without having attempted anything yourself — wait it out, or try from a different network.

Help Center

Getting Started

Extraction & Output

AI Platform Guides

AI Enrichment

Security & Privacy

Pricing & Billing

Use Cases

Troubleshooting

Still have questions?