> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Netcore

The Netcore connector lets your AI agent act in each user's Netcore account. Each user connects their own Netcore access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 33 tools.

**Authentication:** Bearer Token
**Categories:** Communication, Marketing
**Tools:** 33: 14 read, 13 write, 6 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=NETCORE)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Netcore connection

   In **AgentKit > Connections**, create a Netcore connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'netcore'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Netcore:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'netcore_stats_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "netcore"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Netcore:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="netcore_stats_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Netcore credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'netcore_domain_dns_records_get',
  toolInput: {
    domain: '<domain>',
  },
  connector: 'netcore',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="netcore_domain_dns_records_get",
    tool_input={
        "domain": "<domain>",
    },
    connection_name="netcore",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `netcore_domain_dns_records_get`

Get Domain DNS Records · Read-only

Get the DNS records (SPF, DKIM and custom envelope) you must publish to activate a sending domain.
Returns each record's type, host and expected value.
Use this while setting up DNS. Use netcore_domain_verify after publishing the records.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): Sending domain. Example: mail.example.com
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domain":"<domain>"}`

### `netcore_domain_get`

Get Domain Settings · Read-only

Get the configuration and status of one sending domain: DNS setup, tracking settings and verification status.
Returns the domain's settings and status flags.
Use this to check a domain's state. Use netcore_domain_dns_records_get for the DNS records to publish.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_name` (`string`, required): Sending domain to look up. Example: mail.example.com
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domain_name":"<domain_name>"}`

### `netcore_messages_list`

List Email Event Logs · Read-only

List email event logs (processed, sent, open, click, bounce, unsubscribe, spam, dropped and more) for a time range, filtered by recipient, sender, subject, tag or message ID.
Returns event records with message_id, recipient, sender, subject, event, timestamp and details, plus a scrollid for the next page.
Use this to trace what happened to specific emails. Use netcore_stats_get for aggregated counts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `event_start_date` (`string`, required): Event time to start from, in YYYY-MM-DD HH:mm:ss format. Example: 2026-11-12 00:00:00
- `start_date` (`string`, required): Send date to start from. Date in YYYY-MM-DD format. Example: 2026-11-12
- `custom_args` (`string`, optional): Only return events whose send carried this custom argument. Example: campaign=diwali
- `email` (`string`, optional): Only return events for this recipient address. Example: john@example.com
- `end_date` (`string`, optional): Send date to end at. Date in YYYY-MM-DD format. Example: 2026-11-13
- `event_end_date` (`string`, optional): Event time to end at, in YYYY-MM-DD HH:mm:ss format. Example: 2026-11-13 23:59:59
- `events` (`array`, optional): Only return these event types. Example: ["bounce", "dropped"]
- `fromaddress` (`string`, optional): Only return events for this sender address. Example: info@mail.example.com
- `fromdomain` (`string`, optional): Only return events for this sending domain. Example: mail.example.com
- `limit` (`integer`, optional): Records per page, up to 1000. Defaults to 50. Example: 100
- `message_id` (`string`, optional): Only return events for this message ID (from netcore_email_send). Example: a1b2c3d4e5f6
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the log query for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount
- `recipient_domain` (`string`, optional): Only return events for recipients at this domain. Example: gmail.com
- `scrollid` (`string`, optional): Scroll ID from the previous page, to fetch the next page. Example: DXF1ZXJ5QW5kRmV0Y2gBAAAAAAAA
- `sort` (`string`, optional): Sort by send time. Defaults to asc. Example: desc. One of: `asc`, `desc`.
- `subject` (`string`, optional): Only return events for emails with this subject. Example: Your order has shipped
- `tags` (`string`, optional): Only return events for emails with this tag. Example: order-shipped

Example input: `{"event_start_date":"<event_start_date>","start_date":"<start_date>"}`

### `netcore_stats_get`

Get Email Statistics · Read-only

Get summary email statistics (requests, delivered, opens, clicks, bounces, unsubscribes, spam reports and more) for a date range, updated hourly.
Returns counts grouped by day, week, month, tag, sending domain, recipient domain, sender address or subaccount.
Use this for totals and trends. Use netcore_messages_list for per-message event logs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `aggregated_by` (`string`, optional): How to group the numbers. Defaults to day. Example: day. One of: `day`, `week`, `month`, `tag`, `fromdomain`, `recipientdomain`, `fromaddress`, `subaccount`.
- `end_date` (`string`, optional): End of the range; defaults to today. Date in YYYY-MM-DD format. Example: 2026-11-13
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the statistics for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount
- `start_date` (`string`, optional): Start of the range. Date in YYYY-MM-DD format. Example: 2026-11-01

Example input: `{}`

### `netcore_subaccount_credits_get`

Get Subaccount Credits · Read-only

Get a subaccount's current email credit balance and credit settings.
Returns the credit type, available credits and any recurring credit settings.
Use this to check whether a subaccount can still send.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `username` (`string`, required): Subaccount username. Example: brand-a-subaccount

Example input: `{"username":"<username>"}`

### `netcore_subaccounts_list`

List Subaccounts · Read-only

List the subaccounts of your master account, optionally filtered by username.
Returns subaccounts with username, email, status and credit type.
Use this to find a subaccount's username for on_behalf_of or the other subaccount tools.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `limit` (`integer`, optional): Records to return, up to 1000. Defaults to 10. Example: 50
- `offset` (`integer`, optional): Records to skip. Defaults to 0. Example: 0
- `username` (`string`, optional): Only return the subaccount with this username. Example: brand-a-subaccount

Example input: `{}`

### `netcore_suppressed_domain_get`

Get Domain Suppression Status · Read-only

Check whether one domain is on the suppression list.
Returns the domain's suppression status with the date it was first added and last modified.
Use this for one domain. Use netcore_suppressed_domains_list to browse all suppressed domains.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): Domain to check. Example: example.org
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domain":"<domain>"}`

### `netcore_suppressed_domains_list`

List Suppressed Domains · Read-only

List domains on the suppression list, optionally filtered by the date they were last modified.
Returns suppressed domains with their suppression dates.
Use this to audit domain suppressions. Use netcore_suppressed_domain_get to check one domain.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `end_time` (`string`, optional): Only domains modified on or before this date. Date in YYYY-MM-DD format. Example: 2026-11-13
- `limit` (`integer`, optional): Records to return, 1 to 1000. Example: 100
- `offset` (`integer`, optional): Records to skip. Defaults to 0. Example: 0
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount
- `start_time` (`string`, optional): Only domains modified on or after this date. Date in YYYY-MM-DD format. Example: 2026-10-01

Example input: `{}`

### `netcore_suppressed_email_get`

Get Email Suppression Status · Read-only

Check whether one email address is on the suppression list.
Returns the address's suppression status with the date it was added and last modified.
Use this before sending to a single address. Use netcore_suppressed_emails_list to browse all suppressions.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `email` (`string`, required): Email address to check. Example: john@example.com
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"email":"<email>"}`

### `netcore_suppressed_emails_list`

List Suppressed Emails · Read-only

List email addresses on the suppression list, optionally filtered by the date they were last modified.
Returns suppressed addresses with their suppression dates.
Use this to audit suppressions. Use netcore_suppressed_email_get to check one address.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `end_time` (`string`, optional): Only addresses modified on or before this date. Date in YYYY-MM-DD format. Example: 2026-11-13
- `limit` (`integer`, optional): Records to return, 1 to 1000. Defaults to 1000. Example: 100
- `offset` (`integer`, optional): Records to skip. Defaults to 0. Example: 0
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount
- `start_time` (`string`, optional): Only addresses modified on or after this date. Date in YYYY-MM-DD format. Example: 2026-10-01

Example input: `{}`

### `netcore_template_get`

Get Template · Read-only

Get one email template by ID, including its HTML content.
Returns the template's id, name, content and timestamps.
Use this to read a template. Use netcore_templates_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Template ID from netcore_templates_list. Example: 1234

Example input: `{"template_id":"<template_id>"}`

### `netcore_templates_list`

List Templates · Read-only

List the email templates in your Netcore account.
Returns templates with their template_id, name and timestamps.
Use this to find a template_id for netcore_email_send. Use netcore_template_get to read one template's HTML.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `limit` (`integer`, optional): Templates to return. Example: 50
- `offset` (`integer`, optional): Templates to skip. Example: 0

Example input: `{}`

### `netcore_webhook_get`

Get Webhook · Read-only

Get one webhook's configuration: its event URLs and custom headers.
Returns the webhook with its id, events and headers.
Use this to inspect a webhook. Use netcore_webhooks_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `webhook_id` (`integer`, required): Webhook ID from netcore_webhooks_list. Example: 42
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"webhook_id":42}`

### `netcore_webhooks_list`

List Webhooks · Read-only

List the webhooks configured on the account.
Returns each webhook with its id, subscribed events and custom headers.
Use this to find a webhook id. Use netcore_webhook_get for one webhook.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `on_behalf_of` (`string`, optional): Username of a subaccount to run the lookup for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{}`

### `netcore_domain_allocate`

Allocate Domain to Subaccount · Write

Assign an existing, unallocated sending domain to one of your subaccounts.
Returns the result of the allocation.
Use this from a master account after netcore_domain_create. A domain belongs to one subaccount at a time.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain_name` (`string`, required): Sending domain to allocate. Example: mail.example.com
- `subaccount_username` (`string`, required): Username of the subaccount that receives the domain. Example: brand-a-subaccount

Example input: `{"domain_name":"<domain_name>","subaccount_username":"<subaccount_username>"}`

### `netcore_domain_create`

Add Sending Domain · Write

Add a sending domain to your Netcore account with its envelope (custom return path) name and an optional inbound name.
Returns the new domain with the DNS records (SPF, DKIM, envelope) to publish.
Use this to start onboarding a domain, then publish the records and run netcore_domain_verify.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain` (`string`, required): Domain to send from. Example: mail.example.com
- `envelope_name` (`string`, required): Envelope (custom return-path) subdomain for bounces on this domain. Example: bounce.mail.example.com
- `inbound_name` (`string`, optional): Inbound subdomain to configure for inbound parsing. Example: inbound.mail.example.com
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the new domain for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domain":"<domain>","envelope_name":"<envelope_name>"}`

### `netcore_domain_verify`

Verify Domain DNS · Write

Run a DNS check on a sending domain, verifying its DKIM, envelope sender (custom return path) and other records.
Returns the validation result for each record.
Use this after publishing the records from netcore_domain_dns_records_get. A successful check activates the domain.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): Sending domain to verify. Example: mail.example.com
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the check for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domain":"<domain>"}`

### `netcore_email_send`

Send Email · Write

Send an email to one or more recipients through the Netcore Email API from a verified sending domain, with optional personalization, template, attachments, scheduling and tracking settings.
Returns status success with a message_id per request; delivery events follow in netcore_messages_list and your webhooks.
Use this for transactional or bulk sends. Use netcore_templates_list to find a template_id, and netcore_messages_list to check what happened to a message.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `content` (`array`, required): Email body blocks. Each block has a type (html or amp; an amp block must be accompanied by an html block) and the value with the HTML. Placeholders like [%NAME%] are replaced from the personalization attributes. Example: [{"type": "html", "value": "Hi [%NAME%], your order has shipped.
"}]
- `from` (`object`, required): Sender: an object with the sender's email (on a domain that is active in your Netcore account) and an optional display name. Example: {"email": "info@mail.example.com", "name": "Example Store"}
- `personalizations` (`array`, required): One entry per recipient group. Each entry needs a to list of recipient objects (email and optional name) and can add cc and bcc lists, per-recipient attributes that fill [%NAME%]-style placeholders in the content, dynamic_template_attributes, custom headers, tags and attachments. Example: [{"to": [{"email": "john@example.com", "name": "John"}], "attributes": {"NAME": "John"}}]
- `subject` (`string`, required): Subject line. It can contain [%PLACEHOLDER%] attributes. Example: Your order [%ORDER_ID%] has shipped
- `attachments` (`array`, optional): Files to attach to every recipient, each an object with the filename and the file content encoded as base64. Example: [{"filename": "invoice.pdf", "content": "JVBERi0xLjQK"}]
- `bcc` (`array`, optional): Addresses to blind-copy on every message, each an object with an email and optional name. Example: [{"email": "audit@example.com"}]
- `mail_settings` (`object`, optional): Advanced settings: hepf (header and footer), sto (send-time optimisation, which must be enabled on the account first) and amplets. Example: {"hepf": {"enable": false}}
- `priorityflag` (`integer`, optional): Delivery priority: 1 for OTP and transactional, 2 for triggered, 3 for promotional. Defaults to your account setting. Example: 1. One of: `1`, `2`, `3`.
- `reply_to` (`array`, optional): Reply-to addresses, each an object with an email and optional name. Example: [{"email": "support@example.com"}]
- `send_at` (`integer`, optional): Schedule the send for this time, as a UNIX epoch in seconds. Leave empty to send now. Example: 1767225600
- `tags` (`array`, optional): Labels used to group and report on these emails. Example: ["order-shipped"]
- `template_id` (`integer`, optional): ID of a saved Netcore template to use (from netcore_templates_list). You still pass content as a fallback. Example: 1234
- `template_version` (`number`, optional): Version of the template to use, when the template has several. Example: 1
- `tracking_settings` (`object`, optional): Turn click, open and unsubscribe tracking on or off for this send; each setting is an object with enable true or false. Example: {"click_tracking": {"enable": true}, "open_tracking": {"enable": true}}

Example input: `{"content":[{"type":"html","value":"%3Cp%3EHi%20%5B%25NAME%25%5D%3C%2Fp%3E"}],"from":{"email":"info@mail.example.com","name":"Example Store"},"personalizations":[],"subject":"<subject>"}`

### `netcore_subaccount_create`

Create Subaccount · Write

Create a subaccount under your master account; it works like a separate Email API account whose credits the master controls.
Returns the new subaccount.
Use this from a master account to onboard a brand or client. Use netcore_domain_allocate to give it a sending domain.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `email` (`string`, required): Email address of the subaccount owner. Example: owner@brand-a.com
- `password` (`string`, required): Password for the subaccount's dashboard login. Example: S3cure!Passw0rd
- `username` (`string`, required): Username for the subaccount, unique under the master account. Example: brand-a-subaccount
- `credit_type` (`string`, optional): Credit allocation: unlimited, or one_time_credit (the default). Example: unlimited. One of: `unlimited`, `one_time_credit`.

Example input: `{"email":"<email>","password":"<password>","username":"<username>"}`

### `netcore_subaccount_update`

Enable or Disable Subaccount · Write

Enable or disable sending for a subaccount.
Returns the updated subaccount status.
Use this to pause a subaccount without deleting it. Use netcore_subaccount_delete to remove it.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `disabled` (`boolean`, required): true disables the subaccount, false enables it. Example: true
- `username` (`string`, required): Subaccount username. Example: brand-a-subaccount

Example input: `{"disabled":true,"username":"<username>"}`

### `netcore_suppressed_domains_add`

Suppress Domains · Write

Add up to 1,000 domains to the suppression list so Netcore blocks delivery to every address at those domains.
Returns the result of the suppression request.
Use this to block whole domains. Use netcore_suppressed_emails_add for single addresses.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domains` (`array`, required): Domains to suppress (1 to 1000). A leading www. is removed. Example: ["example.org"]
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the suppression for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domains":["example.org"]}`

### `netcore_suppressed_emails_add`

Suppress Email Addresses · Write

Add up to 1,000 email addresses to the suppression list so Netcore blocks every future delivery to them.
Returns the result of the suppression request.
Use this for opt-outs and known-bad addresses. Use netcore_suppressed_domains_add to block a whole domain.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `recipient_emails` (`array`, required): Email addresses to suppress (1 to 1000). Example: ["john@example.com"]
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the suppression for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"recipient_emails":["john@example.com"]}`

### `netcore_template_create`

Create Template · Write

Create a reusable email template from HTML content.
Returns the new template with its template_id.
Use this to save a layout for netcore_email_send. Only the first HTML block is stored.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `content` (`array`, required): Content blocks; only the first html block is stored. Each block has type html and a value with the URL-encoded HTML (up to 10 MB). Example: [{"type": "html", "value": "%3Cp%3EHi%20%5B%25NAME%25%5D%3C%2Fp%3E"}]
- `name` (`string`, required): Unique template name. Example: order_shipped

Example input: `{"content":[{"type":"html","value":"%3Cp%3EHi%20%5B%25NAME%25%5D%3C%2Fp%3E"}],"name":"<name>"}`

### `netcore_template_update`

Update Template · Write

Replace the name and HTML content of an existing email template.
Returns the updated template.
Use this to edit a template. Both the name and the content are required; only the first HTML block is stored.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `content` (`array`, required): Content blocks with type html and the URL-encoded HTML as value; only the first block is used. Example: [{"type": "html", "value": "%3Cp%3EHello%3C%2Fp%3E"}]
- `name` (`string`, required): Template name (unique). Example: order_shipped_v2
- `template_id` (`string`, required): Template ID from netcore_templates_list. Example: 1234

Example input: `{"content":[{"type":"html","value":"%3Cp%3EHello%3C%2Fp%3E"}],"name":"<name>","template_id":"<template_id>"}`

### `netcore_webhook_create`

Create Webhook · Write

Create a webhook that posts email events (delivered, open, click, bounce, unsubscribe, spam, dropped, invalid, scheduled, cancelled) to your URLs.
Returns the new webhook with its id and event mapping.
Use this to receive events in real time. Use netcore_webhook_update or netcore_webhook_patch to change an existing webhook.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `events` (`object`, required): Map of event name to the callback URL that receives it. Event names: delivered, open, click, bounce, unsubscribe, spam, dropped, invalid, scheduled, cancelled. Example: {"delivered": "https://api.example.com/netcore/delivered", "bounce": "https://api.example.com/netcore/bounce"}
- `headers` (`object`, optional): Custom headers Netcore sends with every webhook call, for example an authorization header. Example: {"Authorization": "Bearer token123"}
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the webhook for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"events":{"delivered":"https://api.example.com/netcore/delivered","bounce":"https://api.example.com/netcore/bounce"}}`

### `netcore_webhook_patch`

Update Webhook · Write

Change some of a webhook's event URLs or custom headers, leaving the rest as they are.
Returns the updated webhook.
Use this for small changes. Use netcore_webhook_update to replace the whole configuration.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `webhook_id` (`integer`, required): Webhook ID from netcore_webhooks_list. Example: 42
- `events` (`object`, optional): Event URLs to add or change. Example: {"click": "https://api.example.com/netcore/click"}
- `headers` (`object`, optional): Custom headers to add or change. Example: {"X-Custom-Header": "updated-value"}
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the webhook for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"webhook_id":42}`

### `netcore_webhook_update`

Replace Webhook · Write

Replace a webhook's whole configuration with a new set of event URLs and custom headers; settings you leave out are removed.
Returns the updated webhook.
Use this to reset a webhook. Use netcore_webhook_patch to change only some events or headers.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `events` (`object`, required): Complete map of event name to callback URL. Example: {"delivered": "https://api.example.com/netcore/delivered"}
- `webhook_id` (`integer`, required): Webhook ID from netcore_webhooks_list. Example: 42
- `headers` (`object`, optional): Complete set of custom headers. Example: {"Authorization": "Bearer token123"}
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the webhook for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"events":{"delivered":"https://api.example.com/netcore/delivered"},"webhook_id":42}`

### `netcore_domain_delete`

Delete Sending Domain · Destructive

Remove a sending domain from your Netcore account; it can no longer be used for sending, authentication, tracking or routing.
Returns the result of the deletion.
Use this to retire a domain. This cannot be undone; add the domain again with netcore_domain_create.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain` (`string`, required): Sending domain to delete. Example: mail.example.com
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the deletion for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domain":"<domain>"}`

### `netcore_subaccount_delete`

Delete Subaccount · Destructive

Permanently delete a subaccount.
Returns the result of the deletion.
Use this to remove a subaccount for good. Use netcore_subaccount_update to only disable it.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `username` (`string`, required): Subaccount username. Example: brand-a-subaccount

Example input: `{"username":"<username>"}`

### `netcore_suppressed_domains_remove`

Remove Suppressed Domains · Destructive

Remove up to 1,000 domains from the suppression list so addresses at them can receive email again.
Returns the result of the removal.
Use this to unblock domains. Use netcore_suppressed_emails_remove for single addresses.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domains` (`array`, required): Domains to remove from the suppression list (1 to 1000). Example: ["example.org"]
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the removal for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"domains":["example.org"]}`

### `netcore_suppressed_emails_remove`

Remove Suppressed Emails · Destructive

Remove up to 1,000 email addresses from the suppression list so they can receive email again.
Returns the result of the removal.
Use this to re-enable addresses suppressed by mistake. Use netcore_suppressed_domains_remove for whole domains.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `email` (`array`, required): Email addresses to remove from the suppression list (1 to 1000). Example: ["john@example.com"]
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the removal for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"email":["john@example.com"]}`

### `netcore_template_delete`

Delete Template · Destructive

Permanently delete an email template.
Returns the result of the deletion.
Use this to remove unused templates. A deleted template cannot be recovered.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Template ID from netcore_templates_list. Example: 1234

Example input: `{"template_id":"<template_id>"}`

### `netcore_webhook_delete`

Delete Webhook · Destructive

Permanently delete a webhook so its events stop being posted.
Returns the result of the deletion.
Use this to stop callbacks. This cannot be undone; create a new webhook with netcore_webhook_create.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `webhook_id` (`integer`, required): Webhook ID from netcore_webhooks_list. Example: 42
- `on_behalf_of` (`string`, optional): Username of a subaccount to run the deletion for. Only needed with a master account API key; leave empty to act on the account that owns the key. Example: brand-a-subaccount

Example input: `{"webhook_id":42}`

## Related

Other Communication connectors ([all 132](/agentkit/connectors/?category=communication)):

- [Gmail](/agentkit/connectors/gmail/): Scalekit connector, OAuth, 48 tools
- [Slack](/agentkit/connectors/slack/): Scalekit connector, OAuth, 96 tools
- [Google Calendar](/agentkit/connectors/googlecalendar/): Scalekit connector, OAuth, 30 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
