Railway integration

Developer tools connector, available on Zeplik

Railway is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect Railway and Zeplik can act on your software development for you: Railway is a deployment platform for building and shipping applications with instant deployments, automatic scaling, and managed infrastructure. You stay in the conversation while the assistant does the work in Railway directly.

Zeplik exposes 11 read actions and 7 write actions for Railway. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in Railway without your consent.

Try Railway on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with Railway

Read from Railway (11)

Runs automatically in any conversation.

  • Get deployment logs

    Retrieve runtime logs for a deployment. Use when you need to view the runtime application logs for troubleshooting runtime issues, monitoring application behavior, or debugging errors that occur during deployment execution. This action queries the Railway GraphQL API for runtime log entries associated with the specified deployment ID. The logs are returned in reverse chronological order (most recent first).

  • Get environment

    Get details of a specific Railway environment by its ID, including service instances and deployment information. Use this action when you need to retrieve detailed information about an environment, such as its name, creation timestamp, and the service instances deployed within it, along with their latest deployment statuses. This is a read-only action that queries the Railway GraphQL API.

  • Get git hub pr info

    Get information for a GitHub pull request associated with a Railway service. Use this action when you need to retrieve details about a specific pull request, such as its title, state, URL, or author information, for monitoring PR status or integrating with CI/CD workflows. This is a read-only action that queries the Railway GraphQL API for pull request information linked to the specified service.

  • Get user kickback earnings

    Get the total kickback earnings for the authenticated Railway user. Use this action when you need to retrieve the kickback earnings information for the authenticated user, including the total amount earned and the currency. This is a read-only operation that queries the Railway GraphQL API. Kickback earnings are rewards earned through the Railway referral program when users you refer upgrade their Railway projects.

  • List api tokens

    Retrieve all API tokens for the authenticated user from Railway. Use this action when you need to fetch the list of API tokens associated with the currently authenticated user. This is a read-only operation that returns token metadata including the ID, name, and creation timestamp for each token. The action queries the Railway GraphQL API and returns the complete list of tokens.

  • List environment patches

    Retrieve all patches for a Railway environment using the GraphQL API. Use this action when you need to fetch the list of configuration patches applied to an environment. This is useful for auditing environment history, tracking configuration changes, or reviewing past deployments to an environment. The action queries the Railway GraphQL API for all patches associated with the specified environment ID and returns their metadata including identifiers and timestamps.

  • List git hub repos

    Retrieve a list of GitHub repositories that Railway has access to. Use this action when you need to fetch the list of GitHub repositories associated with the authenticated user's GitHub account through Railway. This is a read-only operation that returns the id, name, and owner for each repository. The action queries the Railway GraphQL API githubRepos endpoint and returns the complete list of accessible GitHub repositories.

  • List git hub writable scopes

    Retrieve the list of GitHub scopes the user has installed the installation to. Use this action when you need to fetch the list of GitHub scope names that the authenticated user has granted to the Railway GitHub application. This is a read-only operation that returns an array of GitHub permission scope strings such as 'repo', 'workflow', or 'read:user'. Note: This endpoint requires account-level authentication, not workspace/project tokens.

  • List integration auths

    Retrieve all integration auths for the authenticated user from Railway. Use this action when you need to fetch the list of integration auths (such as GitHub, GitLab, Vercel, or other connected integrations) associated with the currently authenticated user. This is a read-only operation that returns auth metadata including the ID, name, type, and creation timestamp for each integration. The action queries the Railway GraphQL API and returns the complete list of integration auths.

  • List notification deliveries

    Retrieve notification deliveries for the authenticated user. Use this action when you need to fetch a list of notification deliveries, such as tracking which notifications have been sent (e.g., EMAIL, WEBHOOK, SLACK) and when they were created. This is a read-only operation that queries the Railway GraphQL API. The action supports pagination through the GraphQL edges/node pattern and returns basic notification delivery information including ID, type, and creation timestamp for each delivery.

  • List trusted domains

    Fetch all trusted domains for the authenticated Railway workspace. Use this action when you need to retrieve all trusted domains configured for workspace membership invitations. Trusted domains allow users with emails from those domains to be invited to the workspace without individual invitations. This is useful for auditing existing domain configurations or obtaining domain IDs for deletion operations. This action requires authentication and will return domains from the workspace associated with the provided credentials.

Act in Railway (7)

Runs only after you enable write access.

  • Create plugin

    Creates a new plugin in Railway for the specified project. Use this action when you need to add a custom plugin to a Railway project, such as for integrating external services or extending project functionality. The action requires a valid project ID (found in the Railway dashboard URL) and a descriptive name for the plugin. The plugin will be created with default settings and can be further configured after creation.

  • Delete variable

    Delete a Railway environment variable. This action uses the `variableDelete` GraphQL mutation to permanently remove an environment variable from a project, environment, or service. This action is irreversible — once deleted, the variable cannot be recovered.

  • Delete volume

    Permanently delete a persistent volume and all its associated data from Railway. Use when you need to remove a volume that is no longer needed. This action is irreversible — the volume and all its data will be permanently deleted and cannot be recovered once removed. Use this action when: - Cleaning up unused volumes to reduce storage costs - Removing volumes associated with deprecated environments - Deleting volumes before removing a project

  • Delete workspace

    Delete a Railway workspace and all data associated with it. This action uses the `workspaceDelete` GraphQL mutation to permanently remove a workspace. Use this action when you need to permanently delete a workspace that is no longer needed. This action is irreversible — once deleted, the workspace and all its associated projects, environments, and data cannot be recovered.

  • Disconnect user discord

    Disconnects the authenticated user's Railway account from Discord. Use when you need to unlink a Discord account that was previously connected to Railway for notifications, authentication, or team management. This action is irreversible for the disconnect operation — the user must manually reconnect through the Railway dashboard or Discord OAuth flow if needed.

  • Update project

    Update project settings and configuration on Railway. Use this action when you need to modify project properties such as description, visibility settings, or PR deploy preferences. The following fields can be updated: - description: A brief description of the project - isPublic: Whether the project is publicly visible - prDeploys: Whether pull request preview deployments are enabled This is an idempotent operation — updating a project with the same settings multiple times will not change the result after the first update.

  • Update service instance

    Update build/deploy settings for a service in a specific environment on Railway. Use this action when you need to modify service configuration including commands, healthcheck, replicas, region, and cron schedule. This is an idempotent operation. The following fields can be updated: - startCommand: Custom start command for the service - buildCommand: Custom build command - rootDirectory: Root directory for monorepo setups - healthcheckPath: Health check endpoint path - healthcheckTimeout: Health check timeout in seconds - region: Deployment region - numReplicas: Number of service replicas - restartPolicyType: Restart policy (ON_FAILURE, ALWAYS, NEVER) - restartPolicyMaxRetries: Maximum restart retries - cronSchedule: Cron expression for scheduled deployments - sleepApplication: Enable/disable sleep when idle - dockerfilePath: Custom Dockerfile path - watchPatterns: File patterns for automatic redeployment

How to connect Railway

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try Railway immediately.

  2. Connect Railway

    Open Settings and go to Connectors, then press Connect on Railway. You can also connect from the Railway page in the app.

  3. Add your Railway API key

    Paste your Railway API key when prompted. Zeplik stores it securely on the server and starts working with Railway right away.

Frequently asked questions

Can I use Railway with Zeplik?
Yes. Railway is available as an integration on Zeplik. Connect it once and the AI assistant can work with your Railway account inside any conversation.
What can Zeplik do with Railway?
Once connected, Zeplik has 11 read and 7 write actions for Railway. Railway is a deployment platform for building and shipping applications with instant deployments, automatic scaling, and managed infrastructure.
How do I connect Railway to Zeplik?
You connect Railway by pasting your own Railway API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in Railway without asking?
No. Zeplik reads from Railway by default. Any action that changes data in Railway requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting Railway cost?
Connecting Railway is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related developer tools integrations

Connect Railway to your AI assistant

Every model, one chat. Bring Railway into Zeplik and let the assistant do the work.