Actions

What are Actions?

Actions are custom JavaScript functions that run on the Qik platform's servers. They let you extend the platform with your own business logic — process webhooks from external services, perform complex data transformations, send custom notifications, integrate with third-party APIs, or automate any task that goes beyond the built-in features.

Each action gets its own API endpoint and access token, so it can be called from external services, triggered by events, or run on a schedule.

Creating an Action

To create a new action:

1. Navigate to Developer in the sidebar
2. Click New Action
3. Enter a title and description
4. Write your JavaScript code in the code editor
5. Configure the action's permissions (what it can access)
6. Save the action

Writing Action Code

Actions are written in JavaScript and execute on the server. Your code has access to:

• Request data — The POST body and query string parameters sent to the action's endpoint
• SDK — A pre-configured API client that lets you read and write data in Qik (create content, update profiles, send emails, etc.)
• NPM packages — You can require and use NPM packages for additional functionality

Your action should return a result object. Common patterns:

• {success: true, data: {...}} — Return data to the caller
• {redirect: "https://example.com"} — Redirect the caller to a URL (for GET requests)

Action Permissions

Each action has its own permission sets that control what it can do within the platform. You configure which roles and scopes the action operates under, just like user permissions. This ensures actions can only access the data they need.

The Action Endpoint

Every action gets a unique endpoint URL that can receive GET and POST requests. The endpoint details are shown in the Endpoint tab of the action editor, including:

• The full URL for GET and POST requests
• Required headers (including the action's access token)
• Expected body format
• Webhook URL for external services

Testing Actions

The action editor includes a Testing tab where you can:

• Create test cases with sample input data
• Run the action and see the output
• Validate that the action behaves correctly before deploying it

Always test your actions thoroughly before connecting them to triggers or external services.

Security

Actions can be configured as:

• Secure — Requires authentication to call (default)
• Public — Can be called without authentication (useful for webhooks from external services)

Use Cases

• Webhook handlers — Receive data from external services (payment processors, CRMs, etc.)
• Data processing — Transform, validate, or enrich data when content is created or updated
• Custom notifications — Send tailored emails or messages based on complex conditions
• Integrations — Push or pull data between Qik and other platforms
• Scheduled tasks — Run recurring operations via time triggers

FAQs