Section 1: Content Creation & Lead Generation
Q1: How can I use the Poppy API to automate my content creation process?
A: You can automate your content creation by building a workflow that connects your long-form content to Poppy. The typical process is:
Trigger: Start with your source content, such as a new blog post from WordPress, a video uploaded to Google Drive, a newsletter from Beehive, etc.
Process with Poppy: Use an automation platform like N8N to send the content to a Poppy board. A "System Prompt" in your board will instruct the AI to repurpose it into multiple formats (e.g., social media posts, carousel scripts, video hooks, email snippets).
Output: The generated content is then sent to a destination of your choice, like a Google Sheet for a team member to review, or directly to a social media scheduling tool as a draft.
This allows you to turn one piece of content into dozens of assets, increasing your content volume and consistency.
Q2: Can I build a chatbot to act as a "Lead Magnet" for my business?
A: Absolutely. You can create a chatbot that serves as an interactive Lead Magnet. Instead of a static PDF, your chatbot can provide instant, personalized value—like a mini-consultation, a personalized recommendation, or a quiz that delivers a custom report. This engages potential customers and qualifies them by collecting their information in a natural, conversational way. This requires building a front-end interface with a tool like Lovable or Bolt.
Q3: How do I ensure the AI's responses sound like my unique brand and tone of voice?
A: You train the AI on your voice by providing it with high-quality examples of your content.
Upload Your IP: Add your best content (video transcripts, successful ad copy, email newsletters, blog posts) to a Poppy board.
Create a "System Prompt": In a text box, create a "System Prompt" that defines your persona. Describe your tone (e.g., "expert but approachable," "direct and punchy"), your audience, and your core message.
Reference the Prompt: In your API calls, you will instruct Poppy to always reference this system prompt, ensuring all generated content aligns with your brand voice.
Section 2: Sales, Coaching, & Call Analysis
Q4: Can the API analyze my team's sales calls and provide feedback?
A: Yes. This is a powerful use case. The workflow involves:
Upload Audio/Transcript: You can upload an audio file (MP3) or a call transcript through a custom-built form or automate your meeting recorder to trigger a workflow when a call ends.
AI Analysis: The call transcript is sent to a Poppy board trained on your sales methodology (e.g., principles from the $100M Closing Playbook). The AI can score the call, identify how objections were handled, and suggest specific improvements or questions that could have been asked.
Deliver Feedback: The analysis is then sent back to you or your team member, often via an email or a direct message in a platform like Telegram/Slack.
Q5: Can I build a chatbot that helps handle common sales objections?
A: Yes, but it requires specific training. The AI doesn't inherently know how to close deals. You must teach it your framework. To do this, you would create a knowledge base in Poppy that includes:
Your most common customer objections (e.g., time, money, spouse).
Your specific scripts and reframes for handling each objection.
Examples of successful and unsuccessful conversations.
By training the bot on your closing playbook, it can effectively guide prospects and handle the "Maybes."
Section 3: Building Your AI Application (The Tech Stack & Productization)
Q6: How do I set up a secure login system and paywall for my AI application?
A: This is achieved by integrating a few key tools. Poppy does not handle user authentication directly. The standard tech stack is:
Front-End: An app built with Lovable or Bolt where users interact with your chatbot.
Database & Authentication: Supabase is used to manage user accounts (logins, passwords) and store data securely.
Automation Layer: An automation tool like N8N connects everything. When a user signs up, it can check their payment status in your customer list (e.g., a Google Sheet or CRM) before granting access.
Q7: How do I save the chat history for each of my users?
A: Chat history for a multi-user application should be stored in an external database like Supabase, not within your Poppy board. This ensures each user's conversation is private and secure. Your front-end application (from Lovable/Bolt) will be configured to save messages to and retrieve them from your Supabase database for each specific user.
Q8: How do I keep my Poppy API key and proprietary data secure?
A: Security is critical. The best practice is to use a Supabase Edge Function. This acts as a secure server-side intermediary. Your front-end app calls the Supabase function, which then securely calls the Poppy API on the backend. This ensures your Poppy API key is never exposed to the public, protecting your account and your data.
Section 4: Technical & API Functionality
Q9: What is the difference between Poppy and an automation tool like N8N?
A: Think of it this way: Poppy is the "brain," and automation tools are the "limbs."
Poppy (The Brain): Handles the complex thinking—analyzing data, understanding context, generating content, and making decisions based on your knowledge base.
N8N (The Limbs): Connects Poppy to other applications. It executes the workflow by moving data from one app to another (e.g., taking an email from Gmail, sending it to Poppy, and putting the result in a Google Sheet).
Q10: Can I upload files (like PDFs or videos) directly to a Poppy board through the API?
A: Currently, you cannot add files (like social posts, PDFs, or videos) directly into a Poppy board via the API. This is a high-priority feature in active development, as many users want to add non-text-based assets to their boards programmatically.
The Workaround: The current method is to use an automation workflow. You upload the file to a trigger application (like a form or Google Drive), use a tool in your automation to extract the text or transcribe the audio (e.g., OCR for PDFs, Whisper for audio), and then send that text data to the Poppy API.
Q11: Can the API analyze the visual content of a video, not just the audio?
A: No, not at this time. The ability for the API to analyze visual data from videos is on our priority list, but it is not in the final stages of development. There is currently no workaround for visual analysis. The API's current capability is limited to analyzing the audio transcript of a video.
Q12: Why is my API pulling old data from previous requests instead of using my current prompt?
A: You're likely using the conversation-based API link, which includes chat history. Every time your automation runs, the AI sees the entire conversation thread, including all previous requests you've processed.
The Fix: Switch to the "Knowledge Base Only" API link in your Poppy board settings. This endpoint is stateless. It ignores all chat history and only references the documents you've attached to the board. Each API call is treated as a completely fresh request, so there's no memory of previous data bleeding into new ones.