Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsMailchimp ToolsMailchimp Update Audiences Contacts
Mailchimp Tools

Mailchimp Update Audiences Contacts

Update an existing omni-channel contact in a Mailchimp audience. Use when you need to modify contact details such as language, tags, email/SMS channels, or merge fields.

Write actionRisk level 2 of 5OAuth connection
Use Mailchimp Update Audiences Contacts

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • tagsarray
    An array of tag names to add to the contact. This operation is append-only; existing tags will be preserved, and only new tags from this array will be added.
  • languagestring
    The subscriber's detected language.
  • data_modestring
    Indicates the data processing mode. In `historical` mode, contact data changes do not trigger automations or webhooks. In `live` mode, such changes do trigger them.
  • contact_idstring
    Required
    A unique identifier for the contact, which can be a Mailchimp contact ID or a channel hash. A channel hash must follow the format email:[md5_hash] (where the hash is the MD5 of the lowercased email address) or sms:[sha256_hash] (where the hash is the SHA256 of the E.164-formatte…
  • audience_idstring
    Required
    The unique ID for the audience.
  • sms_channelobject
    SMS channel details for the contact.
  • merge_fieldsobject
    A dictionary of merge fields where the keys are the merge tags. See the Merge Fields documentation for more about the structure.
  • email_channelobject
    Email channel details for the contact.
  • merge_field_validation_modestring
    Defines how merge field validation is handled. When set to `ignore_required_checks`, the API does not raise an error if required merge fields are missing. When set to `strict`, the API enforces validation. If omitted, `strict` is applied by default.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.