Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsEsputnik ToolsEsputnik Get Contact Message History
Esputnik Tools

Esputnik Get Contact Message History

Retrieve a contact's message history across multiple channels from eSputnik. This action returns message history for a specific contact, supporting multiple media types: Email, SMS, Viber, Mobile Push, Web Push, App Inbox, and Telegram. Use this when you need to: - Review all me…

Write actionRisk level 2 of 5API key connection
Use Esputnik Get Contact Message History

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

  • emailstring
    Contact's email address. Either contactId, externalCustomerId, email, or phone must be specified.
  • phonestring
    Contact's phone number. Either contactId, externalCustomerId, email, or phone must be specified.
  • dateTostring
    Required
    End date or datetime for the history period in ISO 8601 format. Supports date format (YYYY-MM-DD) or datetime format (YYYY-MM-DDTHH:mm).
  • offsetinteger
    Offset from the first item for pagination purposes. Default is 0.
  • maxrowsinteger
    Maximum number of items in the response. Default is 10, maximum is 100.
  • dateFromstring
    Required
    Start date or datetime for the history period in ISO 8601 format. Supports date format (YYYY-MM-DD) or datetime format (YYYY-MM-DDTHH:mm).
  • contactIdinteger
    Contact ID number in eSputnik system. Either contactId, externalCustomerId, email, or phone must be specified.
  • channelTypesstring
    Comma-separated list of message channel types to include in the response. Supported types: email, sms, viber, mobilepush, webpush, appinbox, telegram.
  • externalCustomerIdstring
    External Customer ID from your system. Either contactId, externalCustomerId, email, or phone must be specified.

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.