Feature request: Add support for Connect Outbound Campaigns

Abierto
#7,976 11 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@ASHMEET555 ya está trabajando en esto.

Desde el 29/10/2026.

  • #8702 de @ASHMEET555 — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
aws, python
Área
backend

Línea de trabajo

Read the Amazon Connect Lambda invocation documentation linked in the issue, then inspect the project’s existing event-source data classes and batch-processing patterns. Implement typed request and response models for the outbound-campaign event, including parsing the customer-data JSON string once its schema is established. Batch processing is a stretch goal; completion should include focused tests for parsing and event handling if that optional scope is accepted.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

event_sources feature-request parser
Use case

Amazon Connect Outbound campaigns supports invoking a lambda function as part of a journey flow.

This sends a batch of customer profiles for processing

I would like support for this in powertools

Solution/User Experience

I love powerools, pydantic, and types - so would be great to have:

  • event source data classes for the request and the response
  • batch processer support (stretch goal, would love to have).

I am happy to be involved in implementing this.

Details on the lambda function invocation: https://docs.aws.amazon.com/connect/latest/adminguide/lambda-invoke-functions.html It looks like the customer data is a json string that would be good to parse - would be good to get a concrete json schema for this.

Alternative solutions

Acknowledgment
Lenguaje dominante
Python
Estrellas
3.3k
Forks
511
Merge medio
3 d 4 h
PR fusionados (30 d)
98

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aws-powertools/powertools-lambda-python

Todos los issues de aws-powertools/powertools-lambda-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.