ConvertKit
Add subscribers, manage tags, and grow your email list with ConvertKit. In Appbricx, your workflows and server functions call it by name once it is connected.
What you can do
35 actions, each one call from a workflow or a server function. Triggers come from your app: a row changing, a schedule or a webhook.
- Broadcast StatsGet broadcast stats
broadcasts_broadcast_stats - Create BroadcastCreate a new broadcast
broadcasts_create_broadcast - Delete BroadcastDelete a broadcast
broadcasts_delete_broadcast - Get BroadcastGet a broadcast
broadcasts_get_broadcast - List BroadcastsList all broadcasts
broadcasts_list_broadcasts - Update BroadcastUpdate a broadcast
broadcasts_update_broadcast - Add WebhookCreate a webhook automation
create_webhook - Create Custom FieldCreate a new custom field
custom_fields_create_field - Custom Fields: Delete FieldDelete a custom field
custom_fields_delete_field - List Custom FieldsReturns a list of all custom fields
custom_fields_list_fields - Custom Fields: Update FieldUpdate a custom field
custom_fields_update_field - Delete WebhookDelete a webhook automation
destroy_webhook
Set it up
About two minutes, once per project or once for the whole workspace.
- Open Integrations in the builder
Backend panel, Integrations tab, then ConvertKit. To connect it for every project, use Workspace settings, Integrations.
- Add your credentials
An API key (or token) from your ConvertKit account, pasted once. It is stored encrypted and only read on the server when an action runs.
- API key From ConvertKit's settings
- Call an action
From a workflow, by integration id and action name. The call answers with success, output and, when it fails, the reason.
Workflow // .workflow.js (native ctx) export async function run(ctx) { const res = await ctx.integrations.invoke("convertkit", "broadcasts_broadcast_stats", { "broadcastId": "<broadcast id>" }); if (!res.success) throw new Error(res.error); ctx.log.info("ConvertKit answered", { output: res.output }); }
More in Marketing
ConvertKit and its logo are trademarks of their owner, shown only to identify the service this integration connects to. Their use does not imply endorsement by, or affiliation with, that company.