The TDX 2027 Call for Participation (CFP) is officially open.
Every year, TDX brings together the builders and experts turning breakthrough AI into real-world enterprise impact for their teams and customers. AI is changing how we build applications and interfaces. It’s also changing the way our users interact with Salesforce. Agents are now part of business processes, and new, dynamic interfaces can be built at the speed of conversation. The technical decisions behind data, automation, security and integration matter now more than ever.
Today, your chance to help shape that content for the event.
The TDX Call for Participation (CFP) is open now and will remain open until November 16, 2026.
Whether you’re building agents, connecting Salesforce to new experiences, or extending what’s possible with MCP, this is your opportunity to show how business challenges are being solved through your creativity and solutions. This is your moment to show what’s possible and help others level up through real-world experience.
👥 Who should submit?
If your day-to-day includes building, configuring, extending, operating, or implementing solutions across the Salesforce Platform, we want to hear from you.
That includes admins, developers, architects, engineers, solution engineers, product owners, and technical practitioners working across the Salesforce ecosystem and beyond. For admins, familiar responsibilities like maintaining accurate data, configuring permissions, managing automation, and understanding business processes become even more important when agents can act on that information. At the same time, new skills like configuring agents, writing effective instructions and prompts, and testing agent behavior are becoming part of the job.
If you’re solving real problems and learning something others could put to work, this CFP is for you.
🎬 Session types
There’s more than one way to motivate and inspire others with your work.
Breakout sessions (40 minutes)
Breakouts are a great choice when you have a topic that deserves a deeper conversation. Maybe you’ve solved a tricky business problem, found a better way to use Salesforce, or learned valuable lessons from a project. This is your opportunity to walk attendees through your approach, share practical examples, and help them apply what you’ve learned in their own orgs. Plan for about 30 minutes of presentation time, followed by 10 minutes for questions and discussion.
Theater sessions (20 minutes)
Theater sessions are fast, focused, and built for impact. This format shines when you’re demoing a specific product capability, walking through a concise solution pattern, or highlighting a technical insight that lands best when you get straight to the point. Submissions can also include career lessons or thought leadership. While there’s no formal Q&A, presenters typically stay afterward on the show floor to continue the conversation and answer follow-up questions.
Community Networking (45 min)
Community-led networking and peer-learning workshops. Think guided discussions where Trailblazers share challenges, ideas, and perspectives across roles and career stages.
🎯 What we’re looking for
Most of this year’s technical content will come directly from the CFP. We’re prioritizing sessions based on feedback from past events, and what admins are asking to see this year at TDX, on topics including but not limited to:
- Cross-platform solutions that bring several of these capabilities together
- AIforce, headless experiences, and new ways of interacting with Salesforce
- Agent configuration
- MCP servers, tools, and integration patterns
- Agent Script and Agentforce Vibes
- Salesforce APIs and Agent API
- Data 360
- Flow and automation
- Skills and extensibility
- Agentic identity, permissions, security, and trust
- Slack and new ways work happens across Salesforce
This is not the year for high-level overviews. This is the year to show how things actually work.
The strongest submissions usually come from something you built, fixed, improved, or figured out along the way. Show us what the challenge was, how you approached it, what you learned, and what someone else could take back and apply in their own org. A useful demo, a practical lesson, or a hard-earned “here’s what I’d do differently” can be just as valuable as a big idea. If your first thought is, “I wish someone had shown me this sooner,” you may already have a great session.
How to prepare a strong Admin session proposal
I’ll be honest, reviewers read a lot of proposals, and the ones that stick are the ones where the reviewer can tell right away what problem you solved and what the Salesforce Admin will get out of sitting in the room. That’s really the whole test.
- Start with a specific problem. Think about a challenge you actually worked through: an agent that kept giving the wrong answer, a permission model that got out of hand, a flow you had to rethink from scratch. If you hit it, other admins probably will too, and that’s what makes it worth a session.
- Help attendees understand what they will learn. “Attendees will learn how to test agent behavior before go-live” tells me something. “We’ll talk about agent testing” doesn’t.
- Show something you built. Configurations, automations, agent implementations, demos, and the things you’d do differently next time all count. A session built on something you really did is easier to trust, and a lot easier to learn from.
- Keep it practical. If someone can go back to their desk on Monday and try your approach in their own org, you’re in good shape.
- And keep the scope small. Pick one challenge you can explore properly in 20 minutes (Theater) or 40 minutes (Breakout). Trying to cover everything usually means nothing gets covered well.
What goes in each field
Proposed Title. Aim for something that interests admins and makes it obvious what you’ll cover, in [60] characters or fewer. There’s a lot of content competing for attention at TDX, so a clear title beats a clever one that doesn’t say anything. Tip: Be careful with AI-generated titles and abstracts as they often feel overly generic and inauthentic, especially when combined with excessive em dashes.
Proposed Abstract. You get [200] characters for a short paragraph that will be published as the public description of your session, so make it count. Don’t just describe your slide deck. Tell us what you’ll build or demo, what conversation you’ll lead, and what attendees can take back and show their teams. Think WIIFM: what’s in it for them?
Why should this session be presented at TDX? This one matters most. It’s your open letter to the review team, and you have [1,000] characters, so use them. “Admins should know about this” won’t get you far. Tell us what the problem is, who runs into it, what’s different about how you solved it, and why it matters now.
Format. Breakouts (40 minutes) fit deep dives that benefit from audience questions. Theater sessions (20 minutes) fit a focused demo or a single technique. Community Networking (45 minutes) is for guided peer conversation. If you have more than one idea, submit each as its own proposal.
What to skip
High-level overviews and product pitches won’t make the cut. We’re looking for how things actually work. Vague titles and abstracts that name a topic without saying what attendees will gain also tend to fall flat, as do proposals with no demo, example, or real experience behind them. And a thin “why should this be presented” answer undersells even a great idea.
💡 Why submit?
Speaking at TDX is an incredible experience, but the impact goes far beyond the stage.
Impact: Your story helps thousands of builders solve real problems.
Growth: Teaching others sharpens your own thinking.
Visibility: TDX is where great technical work gets noticed.
Community: You’ll meet people who share your passion and curiosity.
Sometimes the session you give in March becomes the solution someone needs in August. That ripple effect is real.
📅 Key dates
CFP Opens: October 28, 2026
CFP Closes: November 16, 2026
Acceptances: Submissions go into review as soon as you submit them. After the CFP closes, we’ll send accept or decline notifications in December, regardless of when you submitted. We can’t offer individual feedback given the volume, but we keep every submission on file for future events. If you’re selected, a session owner will guide you through preparation.
Submitting early never hurts.
🔧 Access speaker support and resources
Once your session is accepted, you and any co-presenters will receive an email prompting you to confirm your participation in the Content Portal. This is where you’ll manage your session details and officially commit to presenting at TDX. You’ll also be added to a speakers-only Slack channel—a dedicated space for updates, deck templates, presentation best practices, and the resources you’ll need to deliver a strong session.
All presenters receive a complimentary speaker pass to TDX. If you already purchased a pass, you’ll receive instructions on how to request a refund or transfer it to someone else.
🗓️ Review the submission selection timeline
After you submit a proposal, you’ll be notified of your session’s status in December, 2026. If your session isn’t selected, don’t lose momentum—there are many opportunities to share your expertise at Trailblazer Community Conferences and Trailblazer Community Group meetings throughout the year. Great content always finds a home.
🚀 Ready to start your submission?
Here are prompts to help you shape an idea:
- What technical challenge did you solve that others regularly struggle with?
- What pattern, integration, or data architecture do you wish you had learned sooner?
- What did you learn the hard way?
- How is your team using Agentforce or Data 360 differently than most?
- What future-state solution or idea could inspire the community?
If your first reaction is, “I’m not sure anyone else has done it quite like this…”—that’s usually the one to submit.
Please reference the FAQ for any additional questions.
👉 Submit here
Ready to submit your session? We can’t wait to see what you bring to the community this year. Let’s build content that keeps delivering long after TDX wraps.
Click to Submit to TDX 2027