How to create Actions

Once authentication is configured, your next step is to create an Action—the task your plugin performs when triggered in a workflow. Actions are responsible for making API calls, sending data, or updating records in the external app.

What is an Action?

An Action defines what your plugin will do in a workflow.

Think of it as:
“When this trigger fires → perform this action.”

For example:

• Send a message via an API

• Create a contact in a CRM

• Update a record in a database

What You’ll Set Up

Here’s what goes into creating a well-functioning action:

• Scopes – (Optional) Define what level of access this action requires

• Input Fields – Let users customize inputs like email, name, message, etc.

• Action JSON – A structured config for the request: method, headers, body

• Perform API – The actual API endpoint that carries out the action

• Output Sample – For mapping results to the next step

Example Scenario

Let’s say you’re building a “Send WhatsApp Message” action:

• Input Fields: recipient number, message text

• Perform API: POST https://api.twilio.com/messages

• Action JSON: Includes headers, body template, auth token

• Output Sample: response with messageId, status, etc.

Best Practices

• Use context.inputData.fieldKey to dynamically pass user input

• Include headers, params, and body in JSON as needed

• Log or return test responses for easier debugging

• Keep action names and descriptions clear and user-friendly

Create Action Demo

Click through a step-by-step, interactive demo walkthrough of Viasocket, powered by Supademo.

https://app.supademo.com/embed/cm66c44pj02ce1xdhl0c5bjyj?embed_v=2