Welcome to our “Embed” tour.
It's a section we particularly love because we believe that anyone should be able to create an app on top of Captain Data.
Here you'll find all the articles you need to start building on top of Captain Data.
We suggest following the list in the order:
- Organizing your workspace & Tips for developers
- Managing Users via our API
- Advanced workflow launch logic & configuration for developers
- Building Chrome Extensions Best Practices
Before you begin
Data modeling and overall processes are pretty important so we'll try to guide you as much as we can here.
Should you have any questions, reach out to your main point of contact or directly open a new ticket on the support.
Global Architecture
Here's a really simplified data model of how it works:
Concepts
Those concepts are critical to understand for the implementation:
- You'll create Users (same as on your SaaS)
- Users have Accounts (connected to integrations like LinkedIn or Hubspot)
- You'll create Workflows that have multiple steps (automated actions) - you should see a workflow as an API route
- When a workflow is launched it creates a Job - a Job is the workflow execution
- A Job needs specific Inputs, Parameters and is generally linked to one or multiple Accounts
- When a Job is finished (success or not) it triggers a Webhook
- The webhook sends, amongst other things, a job_uid that you can use to retrieve Job Results
Checkout our suggestion above to read more on how to embed Captain Data in your app.
Happy automating!