FAQs
Tasks
Q: What are “Tasks” in MagicBlocks?
A: Tasks are predefined actions your AI Agent performs automatically when certain conditions are met — like sending an email, tagging a lead, or pushing data to a webhook.
Q: How do I trigger a Task inside a Journey?
A: Go to your Journey → Actions tab → Add Action, then select Trigger Task. Choose the Task name you created earlier and define the condition that activates it.
Q: Can I reuse Tasks across multiple Agents?
A: Yes. Tasks are workspace-level assets, meaning once you create a Task, you can apply it to any Agent in your workspace.
Functions
Q: What are “Functions” used for?
A: Functions let your AI Agent perform custom logic — like calculations, API calls, or data transformations — mid-conversation. Think of them as “mini-automation scripts” that expand your Agent’s capabilities.
Q: Do I need to code to create a Function?
A: No. MagicBlocks supports no-code function templates for common use cases (like lead scoring, form validation, etc.). Developers can also add custom JavaScript for advanced logic.
Q: Can Functions return data to the conversation?
A: Absolutely. You can return text, numbers, or even formatted JSON objects, which your Agent can reference in replies or future conditions.
Snippets
Q: What are Snippets and how are they used?
A: Snippets are reusable text or prompt blocks that you can insert into any Journey. They help maintain consistent phrasing or responses across Agents.
Q: Can I use dynamic variables inside Snippets?
A: Yes. You can use Dynamic Tokens (e.g., {{lead_name}} or {{company}}) to personalize Snippets per conversation.
Q: Can Snippets contain Actions?
A: No. Snippets are for text or structured prompts only — but they can reference Functions or Key Facts that trigger Actions elsewhere.
Forms
Q: What are Forms in MagicBlocks?
A: Forms are interactive input elements your Agent can use to collect multiple pieces of data at once (like contact forms, surveys, or appointment info).
Q: Can I link a Form to my CRM?
A: Yes. When you create a Form, you can attach a Webhook or Integration Action so submitted data is sent to your CRM, spreadsheet, or marketing platform automatically.
Q: Are Forms required for lead capture?
A: No. You can still collect lead data using Key Facts in conversation. Forms are best when you want structured, multi-field data or custom validation.
Dynamic Tokens
Q: What are Dynamic Tokens?
A: Dynamic Tokens let your Agent insert real-time data (like user name, location, or custom field values) into its responses — making conversations personalized and contextual.
Q: How do I create a new Dynamic Token?
A: Go to Dynamic Tokens → Create New, give it a name, define its data source (e.g., Key Fact, Form input, or external API), and set fallback text.
Q: Can Dynamic Tokens pull live data from APIs?
A: Yes. When paired with Functions or Webhooks, tokens can fetch and display real-time info — such as live pricing, stock availability, or booking times.
Webhooks
Q: What are Webhooks used for?
A: Webhooks let your Agent send or receive data from external systems. They’re ideal for automating lead transfer, CRM updates, or triggering backend workflows.
Q: How do I test if a Webhook is working?
A: Click Test Webhook in the Webhook setup screen. You’ll see a live response preview and HTTP status code (e.g., 200 = success).
Q: Can I trigger Webhooks from inside a Journey?
A: Yes — add a “Trigger Webhook” Action inside your Journey block and define the exact condition (e.g., when all Key Facts are collected).
Q: Does MagicBlocks support authenticated Webhooks?
A: Yes. You can include API keys, Bearer tokens, or Basic Auth headers when configuring your Webhook.
Journey Advanced
Q: What’s inside Journey Advanced?
A: This area gives you developer-level control over Journey logic — such as conditional routing, variable matching, response weighting, and conversation memory handling.
Q: Can I add JavaScript logic directly into a Journey?
A: Not directly — but you can call Functions from Journey Advanced, which allows you to run custom logic safely without exposing code in prompts.
Q: How do I debug complex Journeys?
A: Use Preview Mode + the Robot Head Debugger to see which triggers, rules, or conditions fired during a conversation.
API
Q: What can I do with the MagicBlocks API?
A: You can use the API to:
- Trigger conversations programmatically
- Send or receive messages
- Retrieve lead data
- Update Key Facts dynamically
- Embed MagicBlocks into apps or CRMs
Q: Where can I find API documentation?
A: Go to Advanced Features → API in your workspace or visit the MagicBlocks Developer Portal (if enabled for your plan).
Q: Is there rate limiting on the API?
A: Yes. Free plans have basic rate limits (e.g., 60 requests/minute). Higher tiers offer expanded capacity — see your workspace plan for details.
Best Practices
✅ Keep Functions modular — one clear purpose per function.
✅ Test Webhooks with a mock endpoint before going live.
✅ Use Dynamic Tokens sparingly to avoid long or cluttered responses.
✅ Always name Snippets clearly (e.g., “Greeting_Default” or “CTA_Promo”).
✅ Back up API keys and tokens securely in your integrations panel.