Skip to content
Notis

Get the BotStar app ID when Railway deploys

Avoid hunting through setup notes during a release. Ask Notis to retrieve the BotStar app ID when Railway signals that deployment setup needs it.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Get BotStar Application IDs

Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.

Why this helps

The small but essential app ID can be easy to lose in release notes, slowing down a focused deployment task.

  • Makes the app identifier available at the right release step
  • Avoids manual searching across setup notes
  • Supports repeatable widget initialization

Setup

Build it in a few focused steps.

  • 1Connect Railway and BotStar to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis conversationally for this release-time lookup.
  • 3Describe retrieving the BotStar application ID when the Railway deployment process requests it.
  • 4Select an incoming webhook trigger, choose a run-report channel, and test with one real request.

Questions about this workflow

Does the workflow deploy the app?

No. It retrieves the BotStar application ID for a deployment process that needs to initialize the chat widget.

How does Railway start the workflow?

Configure your release process to send a request to the Notis incoming webhook.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Railway to Botstar. A trigger fires from one place; an action lands in another.

Railway triggers

Botstar actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

BotStar LiveChat onClose Callback

Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get BotStar Application IDs

Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.

ActionInstant

Livechat boot

Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.

ActionInstant

Close BotStar Livechat Widget

Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.

ActionInstant

Livechat on open

Tool to register a callback when the chat window is opened. use after widget initialization.

ActionInstant

Livechat open

Tool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').

ActionInstant

Livechat update

Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.

ActionInstant

Get BotStar Webview Parameter

Tool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.

ActionInstant

Connect any two apps with Notis in the middle.

Railway and Botstar, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Botstar.