Update email campaign activity with the Constant Contact API

Updates the primary_email activity of a campaign in DRAFT or DONE status. It replaces the properties: send the current sender, subject, preheader and lists from Get email campaign activity along with the changes, because what is left out is cleared. html_content and physical_address_in_footer are kept when not sent.

Identifier
constant_contact_update_email_campaign_activity

The request

POST https://connect.reportei.com/api/tools/constant_contact_update_email_campaign_activity/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "campaign_activity_id": "<campaign_activity_id>",
    "from_name": "<from_name>",
    "from_email": "<from_email>",
    "reply_to_email": "<reply_to_email>",
    "subject": "<subject>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
campaign_activity_idstringYesId of the activity with role primary_email, from Get email campaign or Create email campaign.
contact_list_idsarrayNoIds of the lists that receive the email, from List contact lists. Required before scheduling, unless the activity uses a segment.
segment_idsarrayNoThe segment that receives the email, as returned by Get email campaign activity. Send it back to keep it. Never together with contact_list_ids.
from_namestringYesSender name shown to contacts.
from_emailstringYesSender address, a confirmed email address of the account.
reply_to_emailstringYesAddress that receives the replies, a confirmed email address of the account.
subjectstringYesSubject of the email.
preheaderstringNoShort summary shown after the subject in the inbox.
html_contentstringNoNew HTML body, only for format_type 5. Keep [[trackingImage]] inside the body element so opens and clicks are reported.
physical_address_in_footerobjectNoAddress of the sender shown in the footer. state_code is required when country_code is US.

Supported connections

Your customer connects their Constant Contact account once, with one of the modes below. The same connection serves every tool of the toolkit.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/constant_contact, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/constant_contact_update_email_campaign_activity. It becomes your agent's tool definition with no conversion.

Other Constant Contact tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.