Email Octopus List (email_octopus_list_v1
)
Replicate Email Octopus Lists into your database.
To get set up, run this code from the WebhookDB CLI:
webhookdb integrations create email_octopus_list_v1
Source documentation for this API: https://emailoctopus.com/api-documentation
Features
- Dependents
- This replicator is required for the creation of the following dependents:
- Supports Webhooks
- ❌
- Supports Backfilling
- ✅
Schema
Tables replicated from Email Octopus Lists have this schema. Note that the data types listed are for Postgres; when replicating to other databases, other data types maybe used.
Column | Type | Indexed |
pk | bigint | |
email_octopus_id | text | |
name | text | |
created_at | timestamptz | ✅ |
pending | integer | |
subscribed | integer | |
unsubscribed | integer | |
row_updated_at | timestamptz | |
data * | jsonb |
* The data
column contains the raw payload from the webhook or API. In many cases there is no canonical form, like if a webhook and API request return two different versions of the same resource. In that case we try to keep the most coherent and detailed resource.”
Table definition
This definition can also be generated through webhookdb fixture email_octopus_list_v1
.
CREATE TABLE public.email_octopus_list_v1_fixture (
pk bigserial PRIMARY KEY,
email_octopus_id text UNIQUE NOT NULL,
name text,
created_at timestamptz,
pending integer,
subscribed integer,
unsubscribed integer,
row_updated_at timestamptz,
data jsonb NOT NULL
);
CREATE INDEX IF NOT EXISTS svi_fixture_created_at_idx ON public.email_octopus_list_v1_fixture (created_at);