Integrations

Workflow Integrations

Integrations are built-in connectors to popular third-party services. Each connector ships with its own authentication setup, a catalog of methods, and a UI that knows the parameters each method needs. From the workflow's perspective, an integration step looks like any other action — pick a connector, pick a method, fill in the parameters.

Available integrations

The full list grows over time — the action picker in the workflow editor always shows what's currently available. If a connector you expect isn't visible, check that it's enabled for your app or that your subscription tier includes it.

Connecting an integration

The first time you use an integration in a workflow, Tadabase walks you through connecting it. You only need to do this once per app — after the credentials are saved, every workflow in the app can use them.

Authentication methods

Different services use different auth styles. Tadabase handles all of them:

• OAuth 2.0 (Slack, Pipedrive, Monday, Shopify, Xero, Google, etc.) — click "Connect," sign in to the service, approve, and you're done. Tadabase manages the token refresh automatically.
• API Key (Stripe, Airtable, Twilio, SendGrid, Mailchimp, etc.) — paste your API key into the credentials modal.
• Username + password or API token (QuickBase and similar) — credentials are stored encrypted.

Credentials live under Workflows → Manage Integrations. From there you can re-authenticate, rotate keys, or disconnect a service.

Using an integration in a workflow

1. Add a step. In the action picker, scroll to Integrations.
2. Pick the integration (e.g. Slack).
3. Pick the method (e.g. Send Channel Message).
4. Fill in the parameters the method needs. Each parameter shows its type and any allowed values. Use the variable picker to pull values from the source record, a previous step, or the logged-in user.
5. (Optional) Use the Test button to fire a one-off call with sample values, so you can confirm the connector returns what you expect.

The step's response (the parsed JSON the API returned) is exposed to later steps as an Integration Response value — pick this step from the value picker, then drill into the response field you need.

Worked examples

Slack — notify a channel

1. Trigger: Record Created on Orders.
2. Step 1: Slack → Send Channel Message.
   • Channel: #sales
   • Message: "New order #{{order_number}} from {{customer_name}} for ${{total}}!"

Stripe — charge a customer

1. Trigger: Record Updated on Orders, where Status = Approved.
2. Step 1: Stripe → Create Customer (only if customer doesn't already have a Stripe ID).
3. Step 2: Stripe → Create Charge using the customer ID and the order's total.
4. Step 3: Update Record — set the order's Stripe Charge ID and mark it as Paid.

Pipedrive — sync a contact

1. Trigger: Record Created or Edited on Customers.
2. Step 1: Pipedrive → Create or Update Person with the customer's email, first name, last name, and phone.
3. Step 2: Update Record — write Pipedrive's returned person ID back to the customer record.

API Connector (call any REST API)

If a service you need isn't on the list, the API Connector lets you call any REST endpoint. You configure:

• Base URL.
• Authentication (None, API key in header, Bearer token, Basic auth, or custom headers).
• Methods — each one with its HTTP verb, path, query parameters, headers, and body schema.

Once configured, an API Connector method works exactly like any other integration: pick it from the action picker, fill in the parameters, use the response in later steps.

For one-off API calls you don't want to set up a connector for, the Run Custom Code action with fetch is often simpler. Use the API Connector when you'll call the same API from multiple workflows or want a reusable, structured wrapper.

Tips and gotchas

• Each app stores its own credentials. Connecting Stripe in App A doesn't connect it in App B — re-authenticate per app.
• Test before activating. Use the per-step Test button to verify the request works before turning the workflow live.
• Watch for rate limits. Some services (Shopify, Airtable, Mailchimp) rate-limit API calls. If you're processing thousands of records per run, consider pacing the workflow with a Schedule trigger and a smaller batch size.
• Capture failures explicitly. Add a Condition step after an integration call to check the response, and either retry, log, or notify on failure.
• Re-auth periodically. OAuth tokens can be revoked by the user on the third-party side. If a connector starts failing with auth errors, re-connect it under Manage Integrations.