1. Start from the listing​

On AppExchange you can:

• Confirm compatibility with the Salesforce clouds you use (for example Sales Cloud, Service Cloud, and others called out on the listing).
• Review pricing and whether a free trial fits your procurement process (the listing currently describes a 28-day trial option—always confirm on the live listing in case details change).
• Use Try It or install flows Salesforce provides for a sandbox-style experience where that applies.

Bookmark the listing and our LinkedIn updates if you want release- and positioning-level news alongside the docs.

2. Prefer sandbox-first configuration​

Even when a solution is AppExchange-listed and Salesforce-native, integration design is still safest when you prototype in a Sandbox first: fewer surprises for users, easier rollback, and room to align with API and governor limits before production traffic.

Our documentation includes considerations for Salesforce limits and behavior—for example Considerations for Plinqx in Salesforce (version 2 docs)—so architects can sanity-check API usage, events, and order of execution early.

3. Read “Getting started” in the docs next​

Once the package is available in an org you control, the fastest path is:

1. Getting Started with Plinqx — orientation, package models, and support contacts.
2. Post-install and security-oriented articles linked from that section (connected apps, external client apps, and org settings as applicable to your release).

Docs are versioned: use the version dropdown to match the major Plinqx release your org runs.

4. Involve the right stakeholders​

A smooth AppExchange evaluation usually includes:

Plinqx’s pitch is intentionally simple for that conversation: no external Plinqx servers in the middle of your Salesforce data path for the core studio experience—alignment with what we highlight on AppExchange and LinkedIn.

5. Ask us​

• Product and listing questions: support@plinqx.com
• Commercial: sales@plinqx.com (also referenced from the docs)

We will keep Updates here in sync with AppExchange and LinkedIn as the product and listing evolve—so you can treat this site as the how, and those channels as the what’s new.

Happy evaluating.

What the listing emphasizes​

The updated AppExchange presence spells out what teams get when they standardize on Plinqx:

• 100% Salesforce-native — Data and processing stay inside the Salesforce security and governance model you already trust.
• No-code with Flow — Admins and advanced users build and operate integrations with Salesforce Flow and familiar platform tools, not a separate stack to hire for.
• Breadth of connectivity — From everyday business tools (for example Xero, MYOB, QuickBooks) to enterprise and custom endpoints (SAP, Oracle, NetSuite, Workday, Snowflake, AWS, Azure, internal APIs, and more), the goal is one consistent studio instead of a patchwork of one-off connectors.
• Patterns that scale — The messaging aligns with how mature teams design integrations: point-to-point, hub-and-spoke, publish/subscribe, and file-based flows, so you can grow without redesigning from scratch every time.

Those themes match what we share on our company LinkedIn page and what evaluators see on the listing: less custom code, less infrastructure, and full visibility of what ran, succeeded, or failed—inside Salesforce.

Why an AppExchange listing matters​

For many organizations, AppExchange is the approved path to discover, trial, and procure Salesforce solutions. A clear, up-to-date listing helps security, procurement, and admins answer:

• Where does data go? (Staying native is easy to explain.)
• Who can build and support it? (Admins and Salesforce-skilled teams, not only integration specialists.)
• How do we try it safely? (Trial and Try flows on the listing are designed for that.)

What to do next​

1. Open Plinqx on the AppExchange and review highlights, media, and pricing.
2. Use Get It Now or Try It when you are ready to install or pilot in a sandbox-aligned org.
3. For product walkthroughs, use the Watch Demo / video materials on the listing, or reach out via plinqx.com and support@plinqx.com.

We will keep posting milestones on LinkedIn and here under Updates so you always have a single place to match what shipped with how to use it in the docs.

Thank you for building with Plinqx—we are glad to meet you where you already work: on Salesforce.

We're thrilled to introduce our newly revamped Plinqx Documentation website, a comprehensive resource designed to support you through your integration journey with Plinqx. Our goal has always been to ensure that you have access to all the information and tools needed to maximize the benefits of Plinqx. Today, we're taking a step further by enhancing your learning experience and providing easier access to the information you need.

Why the New Documentation Site?​

Our decision to revamp the Plinqx Documentation site was driven by feedback from our community. You asked for a more navigable, informative, and user-friendly platform, and we listened. The new documentation site is not just a repository of information; it's a fully redesigned experience aimed at improving how you interact with Plinqx, whether you're a developer, architect, or business analyst.

Key Features of the New Site:​

• Enhanced Searchability: Quickly find exactly what you're looking for with our improved search functionality. From API references to integration guides, all information is at your fingertips.

• User-Centric Design: The site has been restructured for intuitive navigation, ensuring you spend less time searching and more time doing.

• Comprehensive Guides and Tutorials: Dive into detailed guides and tutorials that cover everything from basic setups to advanced configurations, providing step-by-step instructions to facilitate your Plinqx integration projects.

• Interactive Examples: We've included more code snippets and interactive examples to help you understand how Plinqx components work in real scenarios, enabling you to replicate and adapt these examples to your needs.

• Community and Support: Access our vibrant community and support resources directly from the documentation site. Whether you need troubleshooting help or want to share your insights, the Plinqx community is just a click away.

What's New?​

• Feature Highlights: Discover the latest features and components in Plinqx, including detailed descriptions and use cases to inspire your next project.

• Best Practices: Learn from our compiled best practices on flow design, security, and performance optimization to build efficient and secure applications.

• FAQs and Troubleshooting: Get quick answers to common questions and troubleshooting tips to resolve any issues you encounter swiftly.

We believe this new documentation site will make your Plinqx experience even more productive and enjoyable. It reflects our commitment to providing you with all the resources you need to succeed with Plinqx.

Explore the New Site Today​

Dive in and explore what the new Plinqx Documentation site has to offer. Your feedback is invaluable to us, so as you navigate through the new site, please share your thoughts and suggestions on how we can continue to improve.

Thank you for being part of the Plinqx community. We're excited to support you on your journey to streamlined integration and beyond.

Happy integrating!