Before you create your pipeline, determine the following:
What data you need for your workflow
Determine what information you need to access to complete your process.
Which software services you need to include
Based on where this data is located, decide which cloud-based software services your want to use. In Pipelines, these software products are referred to as channels.
How you want your pipeline to initiate:
Your pipeline can start different ways, including:
On a schedule. You can choose the exact time and/or frequency to run your pipeline.
Manually, by clicking Run pipeline at the top of the page. Running a pipeline manually is particularly useful for one-time data imports. To run a pipeline manually, your first step must be an action or query step.
Trigger based. Your pipeline can initiate based on one of the following:
An external webhook
A data change in a channel
From another pipeline
Your workflow may involve multiple pipelines. They can be organized in a combination of trigger-based and scheduled or one-time run pipelines. A pipeline can call another pipeline.
Quick start pipelines
Quick start pipelines initiate more quickly than standard pipeline trigger actions. This doesn’t change how long they might take to finish running, but planning them for your workflow helps things run more efficiently.
Different workflows can be especially efficient for quick start pipelines. Some examples include:
Single record operations
Replicating, syncing, or entering data manually
Selecting a button
Quick start pipelines must:
Have four or fewer steps
Trigger a few times per minute from human action
Operate on less than 100KB of data
Whether you need to add filters to your steps
You can specify criteria that narrows the data your step returns.
Whether you need to add conditions
Your pipeline can include conditions, such as if-then statements, for-each loops, and stop blocks.
Whether you need to transform your data
You can transform your data, including date-time conversions.
Whether you need more than one pipeline for your workflow
Each pipeline can include only one trigger. If you have a complex workflow you may need multiple pipelines to perform all actions and trigger on all events needed.
For example, a workflow to sync information between Jira and Zendesk could include multiple pipelines.
Can you build pipelines between two different realms of Quickbase?
Yes. Add a user token for each realm and you can pick which realm (account) when you add a step.