Plugin Builder
Getting Started of Plugin Builder
1. Go to viaSocket → Open Plugin Builder → Create New Plugin
Set your:
Plugin Name
Domain (e.g.,
example.com
)
📘 For Detailed Steps, Click here
2. Set Authentication
→ Choose the type of authentication your plugin supports:
🔓 No Auth – for public APIs
🔐 Basic Auth – use API keys or username/password
🔁 OAuth 2.0 – recommended for secure, user-based access
📘 For Detailed Steps, Click here
3. Add Actions and Triggers
→ Define what your plugin does and when it runs:
Actions – API tasks like sending a message or creating a record (POST/GET/etc.)
Triggers – when the plugin fires: poll every X mins or listen via webhook
📘 For Detailed Steps, Click here
4. Test Your Plugin
→ Use the “Test” button to simulate plugin behavior with sample inputs.
→ Validate inputs and response mapping. The header will already be dynamically placed with the API call.
5. Submit or Use Your Plugin
Private – instantly usable in your workflows
Public – submit to viaSocket Marketplace for review and approval
Who is this for?
Developers building native integrations with their SaaS tools
Teams creating reusable actions (e.g. send email, update CRM, create deal)
API-first products that want to plug into automation with no backend logic
Makers building public plugins for the viaSocket marketplace
What Can You Build with Developer Hub?
Private plugins for your team’s workflows
Public plugins others can discover and use
Plugins that support OAuth, Basic Auth, or no-auth public endpoints
Multi-step actions and triggers
Apps with polling or webhook-based event detection
Need Visual Help?
View the Developer Playbook
https://viasocket.my.canva.site/viasocket-dh-playbook
It visually walks you through:
Basic Plugin Details
→ Set the plugin name, logo, and audience visibilityConfigure Authentication
→ Choose how users will authenticate (No Auth, Basic Auth, OAuth 2.0)Add Actions/Triggers
→ Define what your plugin does and when it should runPublish Plugin
→ Once tested, publish as private or submit for public listing on viaSocket
Developer-Specific FAQs
Q: Do I need to host my plugin?
→ No. viaSocket hosts the logic. You just define endpoints and fields.
Q: What’s the difference between Action and Trigger?
→ Actions perform tasks. Triggers listen to events (poll/webhook).
Q: Can I test my plugin without publishing it?
→ Yes. Private plugins can be tested instantly via the Developer Hub.
Q: How is OAuth handled?
→ viaSocket manages token exchange and refresh logic. You configure the URLs.
Q: What does public plugin review include?
→ Security checks, functional testing, and description accuracy.