Home - Creating Your First Action
- Creating Your First Connector
- Creating Your First Data Parser
- Developing Actions
- Creating Your First Action
- Concepts & Best Practices
- Coding Execute Operations
- Coding Variables
- Coding Input Prompt Operations
- Authenticating Actions
- Developing Connectors
- Creating Your First Connector
- Authenticating Connectors
- Reference: Data Connectors
- Extending Slack
- Overview
- Quickstart
- Slack Slash Commands
- Slack Bots
- Workflows with Slack
- Notifications with Slack
- References
- Developer Platform Glossary
- Python and SQL Operations
- Python Operations
- JavaScript Operations
- SQL Operations
- Block Kit Library
Configuring Transposit
When beginning to understand Transposit, it's helpful to know about its high-level functionality and the sequence of tasks in which you'll typically be configuring its toolbox of features, after setting up Transposit, as outlined below.
1. Create Activity Types#
When team members are discussing an incident or task in many places, you would like a single source of truth.
Get started here to create new activity types, such as incidents, tasks, requests, and jobs.
2. Create Runbooks#
Create Transposit Runbooks to document your processes.
Click New runbook to get started and add steps with titles and descriptive text explaining what to do.
3. Automate Actions#
Add automated Transposit Actions to streamline processes, making them more reliable, and reducing manual toil.
Get started here and discover that most of the actions you'll want to automate are a simple API call away.
4. Add Triggers#
Accelerate event response even more with Transposit Triggers that automatically execute a runbook based on set criteria.
Get started here so that, for example, the creation of a Jira ticket or a conversation in Slack will automatically cause your runbook to run.
Now that you have a high-level overview of configuring Transposit, let's see how it is used.